Mackerel blog #mackerelio

The Official Blog of Mackerel

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

Automatically switch themes to match macOS Dark Mode and more

Mackerel team CRE Miura (id:missasan) here.

July has begun and the rain continues to fall, but summer feels like it’s just around the corner.

Since this month marks the end of the 2019 fiscal year, the Mackerel team has been busy revising its long-term plans and putting everything in order for next term like road maps and official events. If I get any news that I’m able to report, I’ll be sure to let you all know through our blog and other social networks.

Now on to this week’s update information.

Automatically switch themes to match macOS Dark Mode

Settings have been added to automatically switch themes to match the appearance (Dark Mode/Light Mode) of macOS Mojave. You can enable/disable automatic theme switching from the user interface of your account settings.


Note that this function is only available for browsers/OS that are appearance mode compatible.

For those of you who are new to Mackerel, you may not have even noticed that themes can be switched in the first place. Mackerel's Dark Mode theme was originally released as an April fools joke in 2015 under the promotional tag “The hacker mode you see in movies”, but was later officially released thanks to such a favorable reception. With this release, it is now possible to have the theme automatically switch to this hacker mode to match the macOS appearance settings.

Changes made to the exception that generates with HTTP errors in mackerel-client-ruby

Changes have been made to the exception that generates with HTTP errors in mackerel-client-ruby v0.8.0. In addition to this, the issue of the exception not being sent correctly when receiving some status codes has been fixed.

AWS Integration now supports EFS and more

Hello! My name is Nishiyama (id:tukaelu) and I joined the Mackerel team as a CRE in May.

It’s hard to believe that 1 month has already passed since the start of the new Reiwa era, and it’s also been 1 month since I joined the Mackerel team. This is my first time bringing you the release announcement! I’m definitely looking forward to seeing you all at future events!

In fact, we participated in the AWS Summit Tokyo 2019 held over three days last week at the Makuhari Messe (from July 12th to 14th).

This year's Makuhari Messe was even larger than last year and still crowded with a large number of visitors. Thank you to everyone who visited the Mackerel booth!


One of our engineers, Watanabe (id:wtatsuru), ran a mini session that attracted quite a few quests.

We’re also planning on participating in the AWS Summit Osaka 2019 at the Grand Front Osaka next Thursday, June 27th. If you’re going to the event, be sure to stop by the Mackerel booth!

Now on to this week’s update information.

Amazon Elastic File System Integration release

AWS Integration now supports Amazon Elastic File System!

With Integration configured, 1 File System = 1 Micro host in Mackerel with a maximum number of 28 metrics.

JAVA_HOME changed to the default search option with mackerel-plugin-jvm

Searching under JAVA_HOME (such as $JAVA_HOME/bin/jps etc.) is now the default when JAVA_HOME is configured as an environment variable in mackerel-plugin-jvm.

If JAVA_HOME is not configured, /usr/bin (such as /usr/bin/jps etc.) will be used as before. If anything other than /usr/bin is specified, you can simplify the specification of command options by configuring JAVA_HOME.

Because this update is an incompatible update, users should note whether or not JAVA_HOME is configured in environment variables when performing this update.

The itemization of hosts can now be checked in the amount of the charge log

From May on, the itemization of Standard hosts/Micro hosts regarding payments is now displayed in the credit card charge log which can be accessed from the organization’s plan tab.

Version display now supported for Amazon Elasticsearch Service Integration

The version of Elasticsearch is now displayed in the ElasticsearchService host information of AWS integration.

Release of ansible-mackerel-agent v0.8.4

  • A task to install mkr command was added
  • Support added for action specification with the check plugin installation task

AWS Step Functions Integration release and more

Hello. Mackerel team CRE Inoue (id:a-know) here.

It is hot outside! For the past week, I’ve been rotating through the same Mackerel T-shirts and polo shirts to try and keep cool. Is summer only going to get hotter from here on out? I'm a little worried.

Now then, on to this week’s update information.

AWS Step Functions Integration release

AWS Step Functions is now supported as as a feature of AWS Integration!

With Integration configured, 1 State Machine can be registered as 1 Micro host in Mackerel (refer here for more on Micro hosts). The formula used to calculate the metric count is 7 + 9 × (number of activities) + 8 × (number of Lambda functions).

Coincidentally, AWS Step Functions is also used in the backend of Hatena Blog, a service provided by Hatena, so there was a lot of excitement in the company over the support for this integration. We definitely recommend all of our Mackerel users to give it a try!

When Anomaly Detection for Roles/training fails, the reason is now displayed

Have you all gotten the chance to try out the recently released public beta version of our new function Anomaly Detection for Roles?

There have been some cases of the training using machine learning algorithms failing under certain conditions, but today's update makes it possible to understand why the training failed.

The Anomaly Detection for Roles function has been highly praised as being effective for understanding workload characteristics such as these, and for helping make monitor configurations more complete. It’s also very easy to set up, so be sure to give it a try if you haven’t already!

“The Confused Deputy Problem” for AWS Integration has been resolved

The External ID for the AWS Integration configuration IAM role is now issued at random.


This solves "The Confused Deputy Problem" and improves the security of integrated roles. You can also improve security by issuing and configuring an External ID for existing AWS Integration configurations.

We’ve also updated the description for the configuration method in the help page, so be sure to give that a second look.

Along with EOL, official support for Ubuntu 14.04 LTS has ended

Along with the support that ended on April 30th of this year, the official support for Ubuntu 14.04 LTS has also ended with Mackerel. Check out the help page linked below for all the officially supported environments.

Other updates

Due to the large number of update content today, I’ll simply list the rest below. - The entry method for credit card information has changed - The card number entry is now easier to understand and more secure than ever. - Changes have been made to the plan page, so that standard hosts and micro hosts that exceed the metric limit can be checked individually

Mackerel designers to present at Hatena Design Hour #7

Mackerel’s two chief designers will be presenting at Hatena Design Hour #7, a web designer event hosted by Hatena.

デザイナーイベント「Hatena Design Hour #7」を開催します #hatenadesign - Hatena Design Group (Japanese only)

At the event, they will be talking on "Mackerel's Dashboard Renewal" and "Creating a character for Mackerel's container-agent". It’s not often that you get the chance to hear directly from the designers regarding their designs and user-friendliness, so if you’re interested, by all means!

Monitor types now in panel display

Mackerel team CRE Miura (id:missasan) here with this week’s update information.

Monitor types now panel display

The Create a New Monitor screen has been updated. Now, the types of monitors that can be created are displayed in a panel for easier viewing.


The various monitors of Mackerel

In addition to threshold monitoring and host connectivity monitoring based on obtained metrics, there are various other monitoring rules available in Mackerel such as URL External Monitoring and Expression Monitoring. Anomaly Detection for roles was also released in March of 2019. Displaying these items in side-by-side tabs has become clustered, so we made this change.

With External URL Monitoring, by accessing published URL in http or https format, you can monitor the response code, response time, character strings included in the response body, as well as monitor the SSL certificate expiration date and more.

Expression Monitoring allows you to customize your metric monitoring, such as monitoring the number of remaining days until the file system capacity runs out, and differences from previous weeks.

Anomaly Detection for roles is still in open beta version, but we are currently fine tuning the function based on user feedback for the official release.

If you haven’t tried all of the monitors yet, we definitely recommend seeing what they all can do. If you’d like to give one a try but don’t know how or find it difficult to use, please contact the support team.

For more information on monitoring and notification settings, see the help page linked below.

debug option added to mackerel-plugin-mysql and more

Mackerel team CRE Miura (id:missasan) here.

The Mackerel team welcomes a new member! Nishiyama (id:tukaelu) joined in May as a CRE! Now we’re really going to step up our CRE activities. You’ll get to know Nishiyama through blogs, technical support, and other meetup opportunities. We’re looking forward it!

Also, be sure to check out the Hatena Developer Blog article below where Inoue (id:a-know) and I talked about being a CRE. (Japanese only)

Now on to this week’s update information.

debug option added to mackerel-plugin-mysql

With the release of mackerel-agent-plugins v0.55.2, the -debug option has been added to mackerel-plugin-mysql. It can be used for diagnosing connection errors etc.

Handling state files is now safer with check-logs and check-aws-cloudwatch-logs

With the release of go-check-plugins v0.30.0, the handling of state files with check-logs and check-aws-cloudwatch-logs has been made even more safe.



Check out the entry linked below for a details regarding check-log behavior. (Japanese only)

Changes made to the output when using the detail option with the mkr wrap command

With the release of mkr v0.37.0, when using the --detail option with the wrap subcommand and a large number of characters exist in the command output, a change has been made to output not only the beginning but the end as well (a total of 1024 characters). Prior to this update, only the beginning was included, but because there may be a description regarding the cause of an error at the end of the output, both the beginning and the end have been included.