Mackerel blog #mackerelio

The Official Blog of Mackerel

A plugin to fetch metrics for AWS Step Functions has been added etc.

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

At last, the long awaited Golden Week begins this weekend! I feel like going to a wide open field or a park with lots of trees to take pictures of the all the lush greenery this Spring season.

During the Golden Week holidays, the Mackerel team will not be offering support, nor will a release announcement be made. For more details on this, be sure to check out the Golden Week Announcement section at the end of this update.

Now on to this week’s update information.

A plugin to fetch metrics for AWS Step Functions has been added

github.com

AWS Step Functions lets you coordinate and visualize multiple components (such as Lambda etc.) as a series of steps. This series workflow is called a state machine.

This plugin supports state machine related metrics. The image below is an actual representation of fetched metrics being visualized.

NVMe device metrics can now be obtained with mackerel-plugin-linux

Metrics for NVMe devices can now be obtained in Disk Read/Write Time as well as Disk Elapsed IO Time with mackerel-plugin-linux (mackerel-agent-plugins v0.48.0).

Additionally, with this release, removable devices are now excluded from metric fetching.

Support window closed / no release announcement during Golden week

The "Feedback" option that is displayed in the upper right corner of the header while logged-in to Mackerel as well as correspondence/inquiries to support @ mackerel.io will be closed during the time period shown below. Inquiries received during this period will be replied to in order on Monday, May 7th.

  • Support window closed period:Apr 28th, 2018 (Saturday) ~ May 6th, 2018 (Sunday) (JST)

The Mackerel development team will also be taking a week off during the Golden Week holiday period.

  • The next update announcement: May 7th (Monday)

Thank you for your cooperation.

User-Agent can now be specified in the HTTP request header for external monitoring etc.

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

We’re already halfway through the month of April and the Mackerel team is gearing up for several upcoming events scheduled for May and June. Also, new giveaway items are in the works, so look forward to that!

Now on to this week’s update information.

User-Agent can now be specified in the HTTP request header for external monitoring

An arbitrary User-Agent can now be specified in the HTTP request header configuration of external monitoring. If User-Agent is not specified or the value is left empty, User-Agent: mackerel-http-checker/x.y.z will be sent (x.y.z represents the version number).

You can now monitor CPU credits spent by the T2 Unlimited feature

AWS Integration as well as mackerel-plugin-aws-ec2-cpucredit (mackerel-agent-plugins v0.47.0) now allow you to obtain CPU credit metrics spent by EC2 instances when the T2 Unlimited feature is enabled .

Elasticache EngineCPUUtilization metrics can now be obtained

You can now obtain Elasticache EngineCPUUtilization metrics in AWS Integration.

The command return time format for mkr hosts has been changed

As was announced last week, with the release of mkr v 0.29.0, the createdAt value included in the execution result of mkr hosts and mkr status has changed to ISO8601 format. Please be aware that these changes will be applied when updating mkr.

Notes displayed in the Host list

Notes can now be displayed in the Host list screen.

Cloud Computing EXPO Japan Spring

Just like last year, Mackerel will once again attend this year’s "Cloud Computing EXPO Japan Spring". The event will be held from Wednesday, May 9th to Friday, May 11th. All of Mackerel’s new business members, including me, will be be there so definitely stop by the Mackerel booth to say hello!

TLS1.0 will stop on June 6th, 2018 (Wed.)

Thank you for choosing Mackerel.

As stated in the title, we will stop encrypted communication via TLS 1.0 on June 6th, 2018 (Wednesday).

Reason for stopping

TLS 1.0 is an outdated encryption protocol and several vulnerabilities have already been confirmed.

PCI SSC, an international organization that defines security standards for credit card payment systems, has required that TLS 1.0 be disabled by June 30th, 2018. *1

In response to this, Mackerel has decided to stop TLS 1.0 communication on June 6th, 2018 (Wednesday).

Impact range

Browsing for mackerel.io will no longer be available with older OS/browsers that do not support TLS 1.1 or later. Additionally, use of the Mackerel API will no longer be available with older OS/OpenSSL environments.

Please consider using Mackerel in official supported environments *2. If TLS 1.1 or later is not yet supported, please migrate to a supported environment.

We apologize for this inconvenience, but we believe that providing our service in a safe environment is of great importance and we hope that you will understand.

Thank you

mkr hosts command return time format to change etc.

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

Starting in April, Hatena welcomed its’ new members to the company and a fresh energy is in the air.

Spring is the season of new things and meeting new people. And on that note, Mackerel is holding Mackerel Drink Up #7 Tokyo on Tuesday, April 24th!

Drink Up is a great opportunity to meet and greet with Mackerel users, contributors, and members of the Mackerel team. We’re all really looking forward to having a good time with all of you, so please apply!

Well then, now on to this week’s update information.

【Pre-release notice】mkr hosts command return time format to change

Please note that the following modifications will be made to the mkr command with this week’s release (the week of April 9th).

The createdAt value included in the execution result of mkr hosts and mkr status will change to ISO8601 format. (Example: 2018-04-09T08:07:06+09:00)

Additionally, the time zone follows the environment in which the command is executed.

host ID now displayed from the GUI

The host IDs that are recorded in the following files can now be seen from the GUI.

  • LinuxOS: /var/lib/mackerel-agent/id
  • WindowsOS: id file inside the installation folder

The ID is now displayed directly under the host name in the host details screen. This will make it more convenient to copy and paste when using in command line or code.

Upgrade option now available with mkr v0.28.0 release etc.

Hello there! My name is Miura (id:missasan) and I recently joined the Mackerel team as a CRE.

It’s been just about a month since joining the company and this is my first update announcement. I think there will be plenty of opportunities to meet and greet at future events and through support contact. I’m looking forward to it!

Now on to this week’s update information.

Upgrade option now available with mkr v0.28.0 release

An upgrade option has been added to mkr command. With this option, file downloading will only be executed when the specified version of the plugin is not installed.

By adding the upgrade option as shown here mkr plugin install --upgrade mackerelio/mackerel-plugin-sample@v0.0.2 and then installing, the following behavior will occur.

  • If a plugin with the same release tag has already been installed, the installation process will finish without downloading.
  • Only when the release tags differ, will the file be downloaded and the plugin binary placed.

Up until now, when running mkr plugin install mackerelio/mackerel-plugin-sample@v0.0.2, the file download would take place regardless of whether a plugin of the same release had already been installed or not. So, when using built-in provisioning tools like Ansible or Chef, the file would download every time, making them difficult to use. Now, with this week’s release of the upgrade option, it’s possible to download only the necessary files.

Additionally, you can also use the upgrade option to downgrade. For example, if v.0.0.2 is currently installed and v0.0.1 is then specified and executed, v0.0.1 will be installed.

A link to the help page was added under the toggle button of the experimental feature setting

If you want to check out what experimental features are available or learn more about them before enabling, we’ve added a link to the help page just under the feature’s toggle button in settings for your convenience.

To learn more about the features available, refer to "Currently provided experimental features" section located at the bottom of the help page.

Currently, there are two experimental features available: Expression monitoring and Displaying customized graphs. If you haven’t used the experimental features yet, by all means, take a look.

Updates for Mackerel related OSS

Updates for various Mackerel related OSS were made this week and the details follow below. A big thanks to everyone who contributed!

mackerel-agent v0.54.1

  • EC2 instance recognition for mackerel-agent has been improved.
  • When starting mackerel-agent, the message outputted when checking host information has been changed from WARNING to INFO.

go-check-plugins v0.19.0

  • [check-ldap] newly added to the package
  • [check-http] The string check option --pattern has been added. This option supports regular expressions.

You can now change the number of display graph columns with keyboard shortcuts etc.

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

I hope you all have had the chance to enjoy the cherry blossoms. I was thinking about going to relax in the park near my house this next weekend, but I'm a little worried they might all be gone by then...

Anyways, now on to this week’s update information.

You can now change the number of display graph columns with keyboard shortcuts

The ability to change the number of display graph columns has been newly added to Mackerel keyboard shortcut feature. The shortcut cheat-sheet can be viewed by pressing ? from the Mackerel screen.

You can increase the number of graph columns (each graph reduces in size) with the [ key, and you can reduce the number of display graph columns (each graph is enlarged) with the ] key. Be sure to try it out.

MemAvailable can now be obtained as system metrics

With last week’s release of mackerel-agent v0.54.0, MemAvailable is now available for relatively new Linux users. A separate announcement regarding this was made last week.

Please check out the blog entry below for more details.

mackerel.io

Release of mackerel-agent v0.54.0

In addition to the MemAvailable support mentioned above, we’ve also made improvements to the process of determining Amazon EC2 instances.

Announcement regarding improvements to mackerel-agent’s Linux memory usage rate calculation method and specification adjustments

As stated in the title, with this week’s release of mackerel-agent v0.54.0, the calculation method for the memory usage rate in the new Linux has changed. With this new support, calculation of the memory usage rate is now more accurate than before. The following are supported.

  • Linux kernel 3.14 or later
  • Or environments where MemAvailable is backported to /proc/meminfo

Specifically, Ubuntu 16.04 or later, Debian 8 or later, CentOS 6.6 or later, Amazon Linux 2014.09 or later, etc.

Along with this, the display and items of stacked graphs for system metric memory regarding the target host have also changed. The specifics are as follows.

  • Existing environments: used + buffers + cached + free = total
  • Target environments: used + available = total

In contrast with existing environments, only “available” is stacked along with “used” and displayed in the target environments. This is due to the fact that the breakdown of Linux memory usage has become more complex in recent years, and “buffers” and “cached” are no longer necessarily freeable memory.

With this change, it is now possible to obtain a more accurate memory utilization rate. However, because there is a possibility that the value trend may change, please take the time to review your monitoring settings and such as necessary.

Thank you for choosing Mackerel.