Mackerel blog #mackerelio

The Official Blog of Mackerel

Improvements are constantly being made to the Mackerel UI

Hello! Mackerel Team Director id:daiksy here.

In Japan, we use the expression “Sankanshion” to describe the changing weather one often experiences around late Winter and early Spring. The temperature changes are intense here, but it seems as though Spring is gradually approaching.

I work from our Kyoto office, and as it gets warmer, this area starts to become more lively with all the cherry blossom viewing and other events.

Here is this week’s update information.

You can now edit directly from the custom dashboard list

Up until now, editing the custom dashboard was done through a permalink, but now we’ve added a button which gives you the ability to edit directly from the list.

In Mackerel, we are constantly making efforts to improve our UI, but these aren’t always included in our weekly announcements. For example, we’ve made it easier to adjust the list screen order to better fit the users’ specific situation, and we’ve also made changes to the on-screen button layout.

Every Scrum Sprint, the Mackerel team holds a UI / UX meeting and we talk in detail about what kind of UI improvements need to be made. We discuss feedback that we’ve received from user inquiries and our actual experience with things we’ve found difficult to use. Although less noticeable compared to some of the larger feature developments, these UI improvement updates are made every week.

Mackerel at JAWS DAYS 2018

jawsdays2018.jaws-ug.jp (Japanese only)

The other day, Mackerel’s very own id:Songmu gave a presentation at the JAWS DAYS 2018 lunch session and talked about hints and other useful ways of using AWS with Mackerel.

To all of you who attended, thank you very much!

Metric graphs can now be displayed in 4 columns etc.

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

Although the morning hours are still pretty chilly, the temperature is finally starting to feel a little spring-like. I’ve never had pollen allergies before, but this year my nose is itchy....... It is not pleasant, and maybe if I ignore it, it will go away.

Now on to this week’s update information.

Metric graphs can now be displayed in 4 columns

As shown in the image above, it is now possible to display metric graphs in four columns. This can be useful when you want to overlook many graphs at once in a high resolution environment like 4K display.

Updates for Mackerel related OSS

Updates for various Mackerel related OSS were made this week and the details follow below.

mackerel-agent v0.52.1

  • Error handling and cloud instance processing were improved.

mackerel-agent-plugins v0.45.0

  • [postgres] xlog_location metrics were added.

mackerel-check-plugins v0.17.1

  • [check-log] Support added for when a file size of 0 is not taken into account.

mkr v0.27.0

  • [monitors] Support added for monitoring rules with a single threshold of either Warning / Critical.

Mackerel at JAWS DAYS 2018

jawsdays2018.jaws-ug.jp (Japanese only)

JAWS DAYS, a festival put on by JAWS - UG, a Japanese AWS user group, will be held at the TOC Gotanda Messe on Saturday, March 10th.

Hatena · Mackerel is also a corporate sponsor of the event!

jawsdays2018.jaws-ug.jp (Japanese only)

I, Inoue (id:a-know), will be one of the presenters during the event’s Lunch Session, and will be talking about hints to help make using Mackerel with AWS more convenient. Please join us!

Notice of database maintenance completion

Mackerel Team Director id:daiksy here.

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

On the day of, maintenance started on schedule at 2:30 p.m. (Japan time) and was completed a little ahead of schedule at 4:47 p.m. We understand that this extended period of system stoppage was an inconvenience and we greatly appreciate your cooperation.

mackerel.io

Maintenance time period

Operations were carried out in the following sequence.

  • 2:30 p.m. ~ 3:30 p.m.: System shutdown and database maintenance implementation
  • 3:30 p.m. ~ 4:47 p.m.: Operation Confirmation

Metrics from mackerel-agent that could not be processed during the system downtime were retransmitted starting at 3:30 p.m. and were all confirmed successfully completed about 30 minutes thereafter.

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.

You can now create monitoring rules with a single threshold of either Warning or Critical etc.

Hello! Mackerel team CRE, Inoue (id:a-know) here with this week’s update information.

You can now create monitoring rules with a single threshold of either Warning or Critical

Monitoring rules allow you to specify the conditions for generating an alert. For example, you can specify ‘Warning’ alerts to occur if the CPU usage rate exceeds 80%, and ‘Critical’ if 90% is exceeded. With this week’s update, it is now possible to create monitoring rules with only a single threshold of either Warning or Critical.

I hope that our users can apply this and put it to good use. Please be aware that support for the CLI tool mkr will come later on.

Focused graphs are now highlighted

When transitioning for the purpose of displaying a specific graph in a format such as https://mackerel.io/orgs/<organization name>/services/<service name>#role=<role name>, that graph is now highlighted.

Role graphs in the service details screen, service metric graphs, and graphs within the graph board are all supported.

cookbook-mackerel-agent has been updated

cookbook-mackerel-agent of Chef's Berkshelf cookbook, has been updated and the following points amended.

  • Now supported with Amazon Linux 2
  • Support with Chef 11 ~ 12.4 and Ruby 1.x has ended in order to prepare for future maintenance

Timed mute can now be set per monitoring rule etc.

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

Last week, we ran a booth at the Developers Summit 2018.

We received a ton of visitors and handed out a lot of the new flyers that were specially made for this event. Helping run the booth, I personally got to meet many people face to face and it was a unique experience. Thank you all very much.

Now on to this week’s updates.

Timed mute can now be set per monitoring rule

Even before this update, it was possible to mute notifications for a specified period of time for all monitoring rules, but now, we’ve made it possible to implement this per monitoring rule.

We think that this can be useful for times when you already know that a problem has occurred or when you want to temporarily suppress notifications for issues that are currently being dealt with.

You can now check the attempt log in alert details when max attempts is configured for check monitoring

We announced an equivalent feature update for external monitoring on February 2nd. With this update, this feature can now be used with check monitoring alerts.

This can be particularly useful for monitoring conditions where alerts can occur for multiple reasons. Give it a try!

Specifications for the average value calculation method of metric monitoring have been adjusted & notes can now be configured in check monitoring etc.

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

"Mackerel Meetup # 11", an official Mackerel event, was held this Monday the 5th. The following is the report that I wrote the day after the event. (Japanese only)

mackerel.io

Even some participants have written blogs about the event. (Japanese only)

blog.lorentzca.me

At the event, we received a lot of helpful comments, impressions, and requests from many different people. Some of them are even already moving quickly within the team. So keep your eye on Mackerel 2018!

Now on to this week’s update information.

Specifications for the average value calculation method of metric monitoring have been adjusted

The other day, an advanced notice was published on this blog announcing the specification adjustment for the average value calculation method of metric monitoring. These adjustments were implemented with this week’s release.

mackerel.io

With this release, average value monitoring is now done using the calculated value based on the number of metric postings. Now, even metrics posted at intervals of 5 minutes that were previously skipped, will be subject to correct average value monitoring.

Notes can now be configured in check monitoring settings

[plugin.checks.ssh]
command = "ruby /path/to/check-ssh.rb"
memo = "This check monitor is ..."

As stated above, it is now possible to configure notes in the check monitoring settings of mackerel-agent. The character string specified here can be checked in alert notifications / the alert details screen / the host details page. Using these notes, you can inform the person receiving the alert about initial operations, monitoring meanings, as well as metric items that should be checked, etc. In order to use this feature, mackerel-agent needs to be updated to the latest version, v 0.52.0.

mackerel-agent now supported with Amazon Linux 2!

mackerel-agent can now be installed on Amazon Linux 2 LTS Candidate (2017.12). Sorry to keep you all waiting!

Updates for Mackerel related OSS

Updates for various Mackerel related OSS were made this week and the details follow below.

mackerel-agent-plugins v0.44.0

  • [aws-elasticsearch] -metric-key-prefix option added
  • mackerel-plugin-aws-s3-requests was newly added
    • The number of requests and latency etc. can now be monitored with S3 bucket with CloudWatch request metrics enabled.

mackerel-check-plugins v0.17.0

  • [ntpoffset] Check processing system was improved
  • [check-tcp] -W option added
    • The error level when an unexpected error occurs can now be fixed at Warning .

Thank you to everyone who contributed Pull Requests!

【2/15 〜 2/16】Mackerel at the 2018 Developers Summit!

Developers Summit 2018, a festival for IT engineers and developers, will be held on Thursday and Friday of next week (February 15th-16th). The Mackerel team’s very own Development Director Kasuya (id:daiksy) and I, Inoue (id:a-know), will be giving presentations at the event. Kasuya will present on the first day (Thursday 2/15) and I will present on the second (Friday, 2/16)!

リモートワークは難しい - それでもぼくらは歯をくいしばってやっていく - Developers Summit 2018 (Japanese only)

「自分」をまるごと活かす!私が“CRE”というキャリアを選んだ理由 - Developers Summit 2018 (Japanese only)

The team will also be running a booth to introduce Mackerel on both days of the event. At the booth, we are preparing a little present give-away, so be sure to come and visit us at the festival!

Graphs can now be shared with people who don’t have accounts etc.

Hello! Mackerel Team Director id:daiksy here.

Here is this week’s update information.

Graphs can now be shared with people who don’t have accounts

Mackerel has a graph sharing feature which allows graphs to be viewed in places other than from Mackerel's Web UI and in various formats such as an image or iframe. However, in order to do this, a Mackerel login account and a login session in the browser was necessary.

With this update, we’ve now released a graph sharing feature that allows anyone who knows the URL to view the graph.

Please be cautious when sharing as the range of disclosure is now wider than ever. Additionally, graphs shared with this feature are assigned new URLs and can be viewed in the shared graphs list.

https://mackerel.io/my?tab=sharedGraphs

You can invalidate the URL of the a shared graph and stop viewer access by deleting the graph from this list.

You can now check the attempt logs in the alert details of external monitoring when max attempts is configured

Up until now, even if the number of maximum attempts was configured, only the log at the moment an alert was opened was displayed in alert details of external monitoring. And because of a mixture of response time deterioration and status code error, it was sometimes difficult to understand why the alert was opened. Therefore, we decided to display all attempt logs, thus making it easier to understand why the alert occurred.

In the screenshot above, you can see that the past 3 minutes of average value monitoring, from 17:44 to 17:46, resulted in an alert condition HIT with 3 consecutive occurrences and shows that the alert opened at 17:46.

We are planning on applying similar improvements for check monitoring as well.

Announcing specification adjustments to the average value calculation method of metric monitoring

Next week we will be adjusting specifications of the average value calculation method for metric monitoring.

For more detailed information, please check out the following announcement.

mackerel.io