Mackerel blog #mackerelio

The Official Blog of Mackerel

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.

The micro host count is now displayed on the plan screen

Mackerel team CRE Miura (id:missasan) here.

Following a long Golden Week holiday, the Reiwa era has officially started. And Mackerel’s first announcement in the new era is about screen display changes following updates made to the billing system starting in May. As you may have already noticed, it is now possible to check the microhost count from the management screen.

Now on to this week’s update information.

The micro host count is now displayed on the plan screen

As stated in the entry linked below, a new billing system started in May.

Along with this, changes have been made so that the microhost count is now displayed from the organization's plan screen in environments using a paid plan.


Now the number of standard hosts, micro hosts, and the metric upper limit excess are all displayed. Check out your plan screen to see the changes. In addition, since these numbers are used to calculate a monthly moving average for your actual billing rate, you can use them as reference.

Please note that the display may differ depending on your subscription (the Free plan for example).

If you have any questions or concerns, please feel free to contact us through your sales manager, a CRE, or using the sales contact form.

The system will temporarily shut down for database maintenance on June 5th (Wed.) at 2:30 pm (JST)

Thank you for choosing Mackerel.

The system will be temporarily suspended for maintenance according to the schedule below. We apologize for any inconvenience that this may cause and appreciate your understanding.

Scheduled date and time

  • June 5th (Wed.) from 2:30 pm - 3:30 pm (JST)


  • Database maintenance

Areas affected during maintenance period

  • Once maintenance has begun, the entire Mackerel system will shutdown for a short period of time.
  • Actual downtime will run about 30 minutes during the time period mentioned above.
  • Web access to Mackerel, data posting by the agent, API access (including the CLI tool), alert notifications, AWS/Azure Integration etc. will be unavailable
  • As soon as maintenance is completed and working operation is confirmed, the system shutdown will end and an announcement will be made
  • As for mackerel-agent metric posting, data will be buffered from mackerel-agent during the maintenance period and resent after maintenance has been completed
    • If resent properly, graphs during the maintenance period will also be displayed.

Regarding Announcements

Situation reports will be made from the Mackerel status page ( as well as from this blog (

Additionally, we’ll also be using our official Twitter account (

For inquiries related to this matter

Please send all inquiries regarding this matter to

Thank you again for your understanding and cooperation. And thank you for choosing Mackerel.

Meet the new container-agent mascot and more

Mackerel Team CRE Miura (id:missasan) here.

To celebrate the recent release of our container-agent, we’ve created a new Mackerel character! As with our existing character agent-si, this new character will appear on service sites, stickers, t-shirts, and other novelty items.

Now on to this week’s update information.

Meet the new container-agent mascot

You’re probably already familiar with Mackerel’s character agent-si. He’s the characterization of mackerel-agent which you install when getting server metrics with Mackerel. (Japanese only)

In February 2019, we released mackerel-container-agent, an agent dedicated for container monitoring. To celebrate, we also released a new character, container-agent-si!


Expect to see the container-agent-si on service sites and novelty items like these stickers. We’ll be passing them out at events!

New stickers! container-agent-si fits right in with agent-si.

container-agent-si was designed by Mackerel team designers id:takuwolog and id:mazco.

container-agent-si is the new mascot of mackerel-container-agent and a sibling to agent-si. As such, you can see some similarities between the two such as their antennae. We used a physical container as a motif for the design, and the sticker’s illustration depicts container-agent-si as if it could transport and put things into a container. Hopefully one of these novelty items will find their way into your hands soon enough!


Specification changes made to the organization’s notification disable setting

As previously announced, changes have been made to the specifications of the organizations’ notification disable setting. Refer to the entry linked below for more details.

SES now supported with AWS Integration and more

Mackerel Team CRE Miura (id:missasan) here.

As was previously announced the other day on this blog, the Mackerel billing system will be updated starting May 2019. A new unit called “micro hosts” will be applied to containers and some cloud components. The price of the micro host has been revised from the previous host unit, and will cost 648 yen (tax included). These revisions to the billing system will make it easier to use containers and various integration functions. For more details regarding the billing system and micro host components, check out the following entry.

Now on to this week’s update information.

SES now supported with AWS Integration

AWS Integration now supports SES. Check out the help page below for more on obtainable metrics and important notes.

Conditions fine-tuned for Anomaly Detection for roles

Detection conditions have been fine-tuned so as to avoid false positives in environments that have little variation from normal such as memory etc.

For details regarding the Anomaly Detection for roles function, refer to the help page linked below.

memory.available can now be displayed in role graphs

Changes were made so that memory.available can now be selected in role graphs. Custom dashboards and more can also be selected.


The issue of text input lag when there are a lot of monitors has been improved

There have been cases of lagging text input, such as contacting the support team, when a large number of monitors are configured in the Monitors page. This behavior has been improved.

The billing system will be updated to support containers and cloud components starting May 2019

Thank you for choosing Mackerel.

Since the recent release of the public beta version of Mackerel’s container agent, the number of cases used in container environments has increased.

In Mackerel’s existing billing system, all components are converted into a unit called a ‘host’ based on usage, and calculated at a rate of 1,800 yen per host. The host unit has a strong connotation as equivalent to one server, and this concept doesn’t really match actual applications with recent container environments and cloud managed services.

So, starting from May 2019, the billing system will be newly revised, dividing the existing ‘host’ billing unit into two separate billing units, standard hosts and a micro hosts.

With the transition to the new billing system, there are no operations or procedures that need to be performed by the user. The new rates will be applied starting in May 2019, thus affecting the bill of June 2019.

Below, we’ll go over some of the details regarding standard host and micro host units.

Standard hosts

Standard hosts will function similar to the current ‘host’ unit. 1 standard host will be charged 1,800 yen (tax included).

The following are billable targets for a standard host.

  • 1 physical server or virtual server installed with mackerel-agent will count as 1 standard host
  • 1 VM system integration (AWS EC2, AzureVM) instance will count as 1 standard host
  • If the number of host metric exceeds 200, every 200 host metrics will count as 1 standard host
  • Every 200 service metrics will count as 1 standard host
  • Every 20 external monitoring items will count as 1 standard host

Micro hosts

Micro hosts are a new billing unit. 1 micro host will be charged 648 yen (tax included).

The following are billable targets for a micro host.

  • 1 pod or task with mackerel-container-agent registered as a sidecar will count as 1 micro host
  • Apart from VM system integration calculated as standard hosts, every AWS/Azure Integration component will count as 1 micro host
  • If the number of host metrics for a micro host exceeds 30, every 30 host metrics will count as 1 micro host

Micro host targets that are currently being charged as regular ‘hosts’ will be automatically change to being calculated as micro hosts starting in May 2019.

If you have any questions or concerns, contact the support team at