Mackerel blog #mackerelio

The Official Blog of Mackerel

Notice of database maintenance completion on 7/18(Wed.)

Mackerel Team Director id:daiksy here.

This is an announcement to report that the planned database maintenance scheduled for July 18th, 2018 (Wed.) was successfully completed without incident.

Maintenance work started on schedule at 3:00 p.m. (Japan time) and was completed at 8:00 p.m. as the result of two extension periods. We understand that this extended period of system stoppage was an inconvenience and we greatly appreciate your cooperation.

Maintenance time period overview

Operations were carried out in the following sequence.

  • 3:00 p.m. ~ 4:30 p.m.: System shutdown and implementation of database maintenance
  • 4:30 p.m. ~ 6:00 p.m.: Confirmation of operation. High-capacity control for retransmission processing from mackerel-agent.
  • 6:00 p.m. ~ 7:00 p.m. :1 hour extension of maintenance period. Continued high-capacity control for retransmission processing from mackerel-agent.
  • 7:00 p.m. ~ 8:00 p.m. : Additional 1 hour extension with only connectivity monitoring component stopped. Observation of mackerel-agent’s retransmission processing and restoration of connectivity monitoring component.

At 8:00 p.m., all features were confirmed re-operational and the maintenance period ended.

This concludes the maintenance report.

Here at Mackerel, we will continue to do our best to maintain a stable work environment for our users in the future. Thank you for your cooperation and thank you for choosing Mackerel.

mkr v0.31.1 Docker Image release etc.

Hello! Mackerel team CRE Miura (id:missasan) here.

Since the end of the rainy season, the heat has been relentless. Everyone please be sure to take good care and avoid heat stroke.

Now on to the update information.

mkr v0.31.1 Docker Image release

Access the Docker Image here. In the future, we plan to provide a new Docker image for each mkr command update. Use it to build development environments and to simplify and optimize version control.

Mackerel Meetup #12 on August 2nd (Thurs.)!

Mackerel Meetup # 12 will be held on Thursday, August 2nd! This time, Drecom was nice enough to let us use their seminar room for the venue.

At the event, user sessions will be held by two guests and the Mackerel team will present on the latest developments and the soon to be released anomaly detection feature.

Come and help us celebrate our achievement of 200 consecutive weeks of releases at this event! (Japanese only)

Retry option added to the mkr throw command

Hello! Mackerel team CRE Miura (id:missasan) here.

We just announced last week that we will no longer be sticking to our previous schedule of consecutive weekly releases, but we already have a new update to deliver. In the future, we would like to actively introduce new update information in this way, by making announcements via this blog and the newsletter when releases are made.

Now on the update information.

Retry option added to the mkr throw command

In mkr v0.31.1, when posting metrics using the mkr throw command, you can now specify to retry failed posts and the number of attempts by attaching the --retry N option. Using this option, you can lower the possibility of data loss when metrics can’t be posted, such as when a request accidentally fails or when Mackerel is under maintenance. Please note that retries will not be carried out if an HTTP error such as 403/404 occurs.

Update the mkr command and give it a try!

Reaching 200 weeks of consecutive feature releases and about Mackerel’s plans for the future

Hello! Mackerel Team Director id:daiksy here.

Last week, Mackerel finally reached its 200th week of consecutive releases! ! !

The road to 200 weeks

The Mackerel service officially launched on September 17th of 2014 and has continued to release new features every week since.

For the Mackerel team, every Tuesday and Thursday are regular release days dedicated to working in some way or another in preparation for that week’s main release. And on every Monday (previously Friday), we publish the content of that week. We prefer to limit the content that is publicized to new features that provide new value to users, and don’t usually include bug fixes and minor modifications. In other words, a new feature of some kind is released every week without fail.

Strictly speaking, the term "weekly" excludes long-term periods of national holiday vacation, such as Golden Week and the New Year's holiday, so "every business week" may be more accurate.

At the time of Mackerel’s launch in September of 2014, the service only had minimal features. For us, starting out as a small product, we believed that it was our mission to deliver new features to users as quickly as possible. And as a result of continuing to do so, we reached 100 consecutive weekly releases in June of 2016.

At that time, the team celebrated and ate Mackerel themed cake!

And now two years later, Mackerel's "weekly feature release" has reached 200 consecutive weeks.

Comments from people involved

Here are a few comments about reaching 200 consecutive weekly releases that we received from some familiar faces.

Current Hatena CTO and founding Mackerel Director, id:motemen

Originally, the idea behind weekly releases started as a lighthearted way to gain momentum during the startup period, but I’m surprised to see that it’s continued for four years now. If you think about it, Mackerel has come a long way!

Previous Hatena CTO and founding Mackerel Product Owner, id:stanaka

Even before Mackerel, one of Hatena's strong points has always been its speed of service development. Likewise, I think that Mackerel has met those expectations with its weekly feature release. I hope that Mackerel continues to meet the expectations of users and that its service can grow by not only focusing on speed, but also by taking on more challenging developments in the future.

Current Product Owner, id:Songmu

I’ve been involved with Mackerel since the beginning of its official release and have been engaged in development as a product owner / manager for a long time, and I am deeply impressed by our achievement of reaching 200 consecutive weekly releases. As a team, we are determined to continue to keep up with the evolution of infrastructure technology around the world, to contribute to service development and operation processes, and provide services that will aid in business growth by continuing to develop new features that can “provide new experiences" as stated in Hatena’s mission statement.

Thank you so much for the comments everyone!

Also, here are a few pictures of the commemorative cakes that were made to celebrate at both the Kyoto and Tokyo office parties last week.

The future of Mackerel

To celebrate last week’s achievement of reaching 200 consecutive releases, we redesigned the Mackerel top page (

This is also to show the development team’s determination to deliver "A new Mackerel for tomorrow".

Mackerel’s development roadmap, which we previously introduced at Meet-up, marked some big updates for the future such as "anomaly detection" and "container support". Now, development for these new features has taken on a new significance for the team.

Throughout the last 200 weeks, the development team has steadily released features that the original product owner had pictured for the service at its launch in September 2014. Now we’re working on the development of new features. These features were not a part of the initial plan, but will make up the feature group of the next generation. Now that we’ve finally finished developing the feature group that the founding product owner had imagined, we’ll be working on a new development roadmap that will lead the next generation of Mackerel.

From here on, the development team will focus on developing these next generation features to further push Mackerel forward.

Reaching an achievement of 200 consecutive weekly releases, we believe that Mackerel has finally finished its first stage of development, which, at the time of it’s launch in September 2014, our goal was to grow the small service as quickly as possible. Now, In order to deliver a new Mackerel to users, we believe that the next step is to take a break from our "Weekly Feature Release", and to focus all of our team’s effort on developing the next big feature.

Our regular release days will continue every Tuesday and Thursday and we will continue to make announcements when new features are released, however the pace at which releases are made may slow down a bit from now on.

We welcome your requests, appreciate your support, and promise to continue putting our full efforts into building the new Mackerel.

Thank you for choosing Mackerel.

200 weeks of consecutive releases! Alert groups feature released!

Hello! Mackerel team CRE Miura (id:missasan) here.

Mackerel's record for consecutive releases has finally reached its 200th week. And we owe it all to you guys. As always, thank you so much for all the pull requests and feedback!

To celebrate this release, we’ve redesigned the Mackerel top page.

Now on to this week’s update information.

Alert groups feature has been released

Up until now, there have probably been quite a few people who have experienced trouble with large quantities of alerts, for example, when a failure occurs in a place that has a wide range of impact such as the network or storage. It can be easy to overlook important alerts that get buried in such large quantities and difficult to grasp their chronological order.

This week we’ve released the “Alert groups” feature that consolidates multiple alerts that occur at the same time into groups, reduces the amount of notifications, and makes it easier to understand the chronological order of alerts.

By configuring an alert group, you can consolidate related alerts into one group by specifying the service, role, or monitor settings.

For more of the specifics, take a look at the following screen in the help page.


In this case, alerts for multiple servers (, and multiple monitoring items (connectivity, URL outline monitoring, custom.sample.foobar) are consolidated into a single group called Example-Service. Creating an alert group makes it easier to see the sequence of troubles that occurred in chronological order and whether or not they’ve been closed. On top of that, since notifications are sent based on the alert group, the problem with inboxes and chat tools being overrun by notifications is solved. By receiving one alert in the alert group, you can simply watch the status of that alert group, making operations more simple.

If you’re unsure about what kinds of things to group, first try creating a group for a role that has multiple hosts. If you don’t have such a role, we suggest trying to setup an alert group for one service.

Create an alert group from the "Create new alert group setting" screen and configure notifications for alert groups in Notification channels.

Be sure to check out the the help page below and give this new feature a try!

On June 28th (Thurs.), browsing for certain documents will be unavailable for a short period of time between 3:00-3:30 p.m.

Thank you for choosing Mackerel.

Mackerel Team Director id:daiksy here.

Due to scheduled maintenance, browsing for several Mackerel documents will be temporarily unavailable during the following time period.

Please note that this maintenance will not affect Mackerel's main service.

We apologize for the inconvenience and thank you for your understanding in our efforts to provide a more stable service.

User authorityType can now be obtained with the API / maintenance notice for Wednesday, July 18th etc.

This is our 199th week of consecutive releases! Only 1 more week until the big 200th!

Hello! Mackerel team CRE Miura (id:missasan) here.

As was announced from this blog the other day, database maintenance will take place on Wednesday, July 18th. Please review for further details.

Now on to this week’s update information.

User authorityType can now be obtained with the API

It is now possible to get user authority information with the API that obtains the user list. Check out the API document below for more details.

Improvements made to mackerel-plugin-aws-kinesis-streams metrics

Problems related to obtaining the following metrics have been fixed.

  • ReadProvisionedThroughputExceeded
  • WriteProvisionedThroughputExceeded

Temporary system shutdown for database maintenance on July 18th (Wed.)

As previously announced, database maintenance including a temporary shutdown of the system will be carried out on Wednesday, July 18th. For more details regarding subject matter and the extent of impact on the day of, please see the blog below.