Mackerel blog #mackerelio

The Official Blog of Mackerel

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【】. 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.

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.

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-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.

-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.

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.

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.

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.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

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.

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.

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.

Amazon Kinesis Data Firehose Integration release

Amazon Kinesis Data Firehose now supported with AWS Integration.

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.

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.

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 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.

mackerel-container-agent has been updated

Hello. CRE Nishiyama (id:tukaelu) here.

Today is another humid one.

At home I’ve been running the air conditioner and the dehumidifier. With Mackerel, I’ve been able to monitor my room temperature and humidity, but recently I’ve started to worry about my electricity bill. Maybe I should start monitoring the amount of electricity I use as well.

This week’s release content concerns mackerel-container-agent!

mackerel-plugin-json now included

Although mackerel-plugin-json was not included as an official plugin, it has now been added to the plugins bundled with mackerel-container-agent.

This plugin is really useful when monitoring with endpoints that respond in JSON format such as the "Health Endpoint Pattern" mentioned in "Introductory Monitoring".

This plugin will be particularly useful in a lot of cases regarding container operation and monitoring. I definitely recommend giving it a try!

The region can now be resolved when the configuration file URL is S3 specified

The region error that occurred by specifying s3:// in the external configuration file of the container agent when the environment variable AWS_DEFAULT_REGION is not set has been fixed.

The configuration file can now be read at fixed intervals

The configuration file can now be reloaded in fixed minute intervals by configuring MACKEREL_AGENT_CONFIG_POLLING_DURATION_MINUTES in the environment variables of mackerel-container-agent,

For more information, be sure to refer to the manual explanation as well!

Mackerel at CloudNative Days Tokyo 2019 (July 22-23)!

Mackerel will be running a booth at CloudNative Days Tokyo 2019 held at Toranomon Hills Forum for two days from July 22nd to the 23rd.

Today from 4:40pm - 5:20pm (JST) in RoomH, Mackerel team SRE Imai (id:hayajo_77) will be presenting on "The strategy behind the development of the Mackerel team's container agent and future plans"!!

Also, the CRE team will be preparing a demo environment with novelty goods in the Exhibition AREA on the 5F, so be sure to stop by the Mackerel booth if you’re coming to the event!

We hope to see you there!!

The channel settings screen can now be opened directly from the side menu

Hello. CRE Inoue (id:a-know) here. Now that the rainy season has begun, the heat and humidity are in full swing. I hope everyone out there is able to keep cool.

Recently, I’ve only been craving cold food, and apparently that can be a barometer for summer fatigue. It would be nice if I could "monitor" what and how much I eat and drink this summer. Lol

Now on to this week’s releases.

The channel settings screen can now be opened directly from the side menu


As you can see, Channels has been added to the side menu. Now you can open your channel settings screen directly from here. We hope this makes things more convenient!

New metrics obtainable with the mackerel-plugin-aws-batch plugin

The metrics SUCCEEDED FAILED have been added as metrics that can be obtained with the mackerel-plugin-aws-batch plugin. This plugin can be installed with the mkr plugin install command. For more details, refer to the following help page.

Mackerel at CloudNative Days Tokyo 2019(7/22〜23)!

The Mackerel team will be running a booth at CloudNative Days Tokyo 2019 , which will be held at Toranomon Hills Forum for two days from July 22nd (Mon) to the 23rd (Tuesday). That’s next week!

Mackerel team SRE Imai (id:hayajo_77) will be taking to the stage and presenting on the topic titled ‘The strategy behind the development of the Mackerel team's container agent and future plans’. The presentation will be an overview of Mackerel's container environment and other things considered during development.

Me and the other CREs will be running the Mackerel booth set up with a demonstration environment in the Exhibition AREA on the 5th floor. We’ll also have stickers and new novelty goods, so be sure to stop by! Lol

I’m really looking forward to seeing as many of you as possible at the event!

Anomaly Detection for Roles will become a paid feature starting August 2019

Thank you for choosing Mackerel.

The other day, the beta version of Anomaly Detection for Roles was released for Mackerel.

Based on the feedback we’ve received up to this point and improvements made, we believe that the quality of this function has satisfied a certain level and have decided to officially provide the feature starting August 2019.

As an official feature, we will no longer offer the free campaign during the beta trial period.

The action of becoming an official feature does not require any special operation from the user. If you continue to use Anomaly Detection for Roles, it will automatically switch to the official version and charges will incur.

Charge settings and settlement timing for Anomaly Detection for Roles

Anomaly Detection for Roles will be charged at a rate of 1,800 jpy for every five standard hosts that are registered in a monitored role. The number of standard hosts will be calculated on a moving average of one month, taking into account auto scale and so on.

For example, if six standard hosts are registered in role A, and Anomaly Detection for Roles is configured for role A, using the conversion 2 units x 1,800 jpy, a charge of 3,600 jpy will be applied. This calculation is done on a per-role basis. For example, if the same Standard Host is registered in multiple roles, it will be counted for each role.

Role A Role B
Standard Host V, W, Z Standard Host X, Y, Z

In the above example, Standard Host Z overlaps in roles A and B. This will count as 6 Standard Hosts for Anomaly Detection for Roles.

The Anomaly Detection for Roles function will be officially provided starting August 1st, 2019. Usage charges for the month of August will be applied to September’s settlement.

You can check how many Standard Hosts are currently being counted for Anomaly Detection for Roles from your account’s Plan tab (

If you have any questions or concerns, please feel free to contact us at