Mackerel blog #mackerelio

The Official Blog of Mackerel

go-check-plugins update

Hello. Mackerel team CRE id:a-know here bringing you this week’s updates.

go-check-plugins update

go-check-plugins has been updated to v0.32.0. The following functional changes were made.

  • [check-http] Authentication information for Basic authentication can now be specified in the form of --user USER:PASSWORD
  • [check-procs] The --pattern option can now be specified multiple times. The following is a usage example.
$ check-procs -p "sshd" -p "bash"
Procs OK:
Found 5 matching processes; cmd /sshd/
Found 2 matching processes; cmd /bash/

Thank you to everyone who contributed!

We’ve increased the number of seats for Mackerel Drink Up #9 Tokyo on October 23rd!

Due to high interest, we’ve increased the limited number of spots available to attend the recently announced Mackerel Drink Up #9 Tokyo!

mackerelio.connpass.com (Japanese only)

The theme of this event is “Recent Updates”. Thankfully, the LT quota has already been filled. There are still a few spots left, so please consider taking a break in the middle of the week and join us!

The release of the Alert Status widget and more

Hello. CRE Nishiyama (id:tukaelu) here.

The rugby world cup is really heating up. With Japan’s upset over Ireland, I really hope that they can advance for the first time!

Now on to this week’s update information.

The release of the Alert Status widget

The Alert Status widget has been added to the widgets available for custom dashboards.

f:id:mackerelio:20190930102506p:plain

With the Alert Status widget, you can display the alert statuses of all the hosts that belong to that role, arranged in order of Unknown, Critical, Warning, OK, and you can access each host details screen by clicking on their icons.

This makes it easier to keep an eye on host statuses and is particularly handy when numerous hosts belong to one role!

This function was actually implemented by students who participated in the Hatena Internship program, so be sure to try it out!!

mackerel.io

Display of the date and time at which monitors are created/updated is now supported

The date and time at which a monitor is created/updated is now displayed.

f:id:mackerelio:20190930102559p:plain

The date and time at which a monitor was last updated is displayed from the Monitors list and both the date and time at which a monitor was created and last updated are displayed at the top of the monitor’s details page.

The registration error when a NIC name cannot be retrieved with Mackerel-agent for Windows has been resolved

Previously, a host registration error would occur when the NIC name could not be retrieved, but this problem was corrected with the mackerel-agent v0.63.0 to register without the unnamed NIC.

Mackerel’s 5 year anniversary!

Thank you for choosing Mackerel.

Mackerel Director id:daiksy here.

Mackerel was officially released just five years ago on September 17th, 2014. The beta was first released in May of that year and received it’s official release after a four-month trial period. The director at that time was Hatena's current CTO, id:motemen, and this was all about two months before I even joined Hatena.

mackerel.io (Japanese only)

Back then, functions for service metrics monitoring and Slack notifications were still under development, but new functions were released every week based on the idea of starting out a service small and then growing it quickly.

If you take a look back at the Meetup report following the official release, you can get a glimpse of what it was like back then.

mackerel.io (Japanese only)

After that, Mackerel's weekly feature releases would continue for 200 consecutive weeks.

mackerel.io

And although there have been considerable changes in the environment surrounding system operation over the past 5 years, feedback from users like all of you has inspired the concepts for functions like mackerel-container-agent, Micro hosts, Anomaly Detection for Roles, etc., and has allowed us to continually improve and keep up with changes of time.

f:id:mackerelio:20190422193104p:plain

We look forward to seeing how another 5 years will shape the evolution of Mackerel.

Help us celebrate at some of the events we have planned out around the end of this year!

Downtime feature release and more

Hello. CRE Miura (id:missasan) here.

For a long time now we’ve been receiving many enthusiastic requests to release a downtime function that allows the user to stop monitoring at a specified time!

Leading up until now, Mackerel has had several functions for suspending monitoring or notifications, but in order to respond to scheduled batches and maintenance etc., the use of a separate scheduler function was required like with cron for LinuxOS, taking time and effort. With the release of this downtime feature, it is now possible to set up flexible schedules from Mackerel. And of course, it can also be configured from the API.

The Mackerel team is pleased to be able to provide a function that is directly connected to saving users time and effort. In addition to this, if there are changes that you would like to see made to other functions, please feel free to send us some feedback at【support@mackerel.io】. For open source related items, pull requests are also welcome!

Now on to this week’s update information.

Downtime feature release

We’ve released a function that allows you to suspend monitoring for a specified time period, for a target service/role or monitor. Recurrence settings such as hourly, daily, weekly (day of the week), monthly, and yearly are also available.

During the downtime’s configured time period, incidents will not appear on the alert list nor will notifications be sent to the notification channel, even if there are metric posts that conflict with the target monitor. (Metrics will be posted)

As described in the following use cases, this can be used in advance for load increases or for instances when the service is known to stop.

Use cases

  • Periodic batch processing
  • Scheduled maintenance periods

How to use

Downtime can be configured in the following two ways.

  • From the console screen
  • From the API

For more detailed information, check out the help page below.

https://mackerel.io/docs/entry/howto/downtimesmackerel.io

Alert Group Settings API release

Alert Group Settings can now be obtained, created, updated, and deleted from the API.

For more details, check out the help page below.

mackerel.io

WebSocket now supported with AWS Integration API Gateway

WebSocket related metrics can now be obtained. Check out the following help page for more details regarding obtainable metrics.

mackerel.io

mackerel-plugin-solr now supports retrieving metrics for Apache Solr 7.x and 8.x

With mackerel-agent-plugins v0.58.0, Apache Solr 7.x and 8.x metrics can now be obtained in addition to the previously obtainable 5.x and 6.x.

github.com

-redis-namespace option added to mackerel-plugin-sidekiq

Also in mackerel-agent-plugins v0.58.0, the -redis-namespace option has been added to mackerel-plugin-sidekiq, and the key namespace can now be specified. If you use a gem like redis-namespace to give the Redis key a namespace, you can now get metrics by specifying this option.

github.com

Top-level tagging with Amazon API Gateway now supported and more

Hello. Mackerel team CRE Inoue (id:a-know) here. Recently, the summer heat has finally started to cool down.

Now let’s take a look at the update information that has come out since our last announcement.

Top-level tagging with Amazon API Gateway now supported

This is an announcement regarding the integration of API Gateway with Mackerel AWS Integration.

mackerel.io

When API Gateway integration was released in November 2018, Amazon API Gateway only supported tags on Stages. For this reason, Mackerel also filtered using APIs that included stages.

In May 2019, Amazon API Gateway began tagging support for all top-level resources.

aws.amazon.com

With this, Mackerel will also begin to offer the same support starting September 5th. The filter conditions for Mackerel's API Gateway integration will change as follows.

  • Tags will no longer be filtered by Stages
  • Only API tags will be targeted for filtering.

As a result of these changes, charges regarding API Gateway integration may fluctuate slightly. We apologize for the inconvenience to those of you currently using the service, but we will be reviewing the filter conditions around September 5. (For those of you already using API Gateway integration as of August 23, we have also contacted you directly.)

The release of mackerel-agent v0.62.0

The main changes in v0.62.0 are as follows.

  • The metadata plugin now supports the environment variable MACKEREL_PLUGIN_WORKDIR
  • Posting of unused system metrics (memory.active , memory.inactive) has been stopped
    • If you are currently monitoring these items, please pay attention to the monitoring settings when updating the agent.
  • The process command name is now checked when checking the pid file.
    • This fixes the bug where mackerel-agent would not start up when the previous pid file is unintentionally left over and the OS is restarted.

Prices to be revised due to the consumption tax rate change

Thank you for choosing Mackerel.

Due to the consumption tax rate changing from 8% to 10% starting October 1, 2019, the price of our Standard plan will also change in the following ways starting in October 2019.

  • Standard Host unit cost

    • Previously 1,800JPY(tax included)
    • Revised cost 1,833JPY(tax included)
  • Micro Host unit cost

    • Previously 648JPY(tax included)
    • Revised cost 660JPY(tax included)

The new prices will be applied to the billing at the beginning of November 2019. October’s billing will cover September’s usage, so the prices will use the previous tax rate.

If you have questions or concerns, please feel free to contact us at support@mackerel.io

Thank you

The official release of Anomaly Detection for roles and more

Hello. CRE Miura (id:missasan) here.

This week is packed full of new announcements like the official release of Anomaly Detection for roles, AWS Integration support for Amazon Kinesis Data Firehose, OSS updates, and the Obon holiday break... so be sure to read until the end!

Now on to this week’s update information.

The official release of Anomaly Detection for roles

The Anomaly Detection for roles function has officially been released. With this, as was previously announced the other day, usage of this function will incur charges starting from August 2019. The ability to check the functions usage status will be available from the Plan tab in your organization’s detail screen starting early August.

Check out the following blog post for more information about billing.

mackerel.io

The following features have also been released.

Support for Mackerel API

Anomaly Detection for roles can now be operated from the Mackerel API. This can be used with the Monitor configuration API and the Alerts API.

mackerel.io

Support for mkr command

With mkr v0.39.0, Anomaly Detection for roles can now also be operated from mkr command.

With a monitor configured for Anomaly Detection for roles, monitor information and alerts will be displayed in the mkr monitors and mkr alerts results. Configuration changes with the diff, push, and pull subcommands are also supported.

mackerel.io

Amazon Kinesis Data Firehose Integration release

Amazon Kinesis Data Firehose now supported with AWS Integration.

mackerel.io

When integrating with AWS integration, billable targets are determined using the conversion 1 delivery stream = 1 Micro host. Up until now, it was possible to collect metrics using the plugin if you set up a metric collection instance etc., but now with integration, it’s even easier to visualize metrics in Mackerel. Be sure to give it a try!

custom_identifier now supported with check-plugin

custom_identifier is a configuration that allows the user to assign a unique identifier to the host and can be specified in the plugin’s settings. By using this, monitoring results can be sent as a monitor of the specified host instead of the host on which mackerel-agent is running.

With mackerel-agent v0.61.1, custom_identifier can now also be used for check monitoring. For example, when using check-mysql to check the connection from the Web server to the DB server, you can post this result as that of the DB server.

For more details, check out the following help page.

mackerel.io

CGC and CGCT metrics added to plugin-jvm

With mackerel-agent-plugins v0.57.0, CGC and CGCT metrics have been added to mackerel-plugin-jvm. This also addresses the metric retrieval error issue when using SerialGC.

github.com

Support Window closed during the Obon holiday from August 13th-15th

Official Mackerel support (the "Feedback" option displayed in the upper right corner of the header while logged-in to Mackerel as well as correspondence/inquiries to support@mackerel.io) will be closed during the Obon holiday through the following dates.

Support window period of closure:Aug. 13th, 2019 (Tues.) ~ Aug. 15th, 2019 (Thur.) (JST)

Inquiries received during this period will be replied to in order on Friday, August 16th. Thank you for your cooperation.