Response time measurement specifications adjusted for URL external monitoring・ Temporary countermeasures for .io domain malfunctions to be restored etc.

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

It’s starting to get pretty cold outside. Plus, it seems like we are in for some rain. People often refer to server monitoring as “a health examination for your server”, but since the seasons have changed, we should all probably take care of our physical health as well.

Anyways, here is this week’s update information.

Response time measurement specifications adjusted for URL external monitoring

As announced on this blog the other day, response time measurement specifications for URL external monitoring were adjusted on October 12th, as scheduled.

The following two points were adjusted.

  • DNS name resolution time is no longer included in URL external monitoring response time measurement
  • Response time is no longer recorded if the HTTP response does not return

When monitoring response times, be sure to keep an eye on metrics and adjust thresholds as necessary.

【Notice】Countermeasures taken in response to .io domain malfunction to be restored

As announced in the above entry, countermeasures taken by Mackerel in response to the .io domain malfunction will be restored. The judgment interval for Mackerel's connectivity monitoring has been set to an interval longer than the negative cache TTL and is scheduled to be restored to its’ original interval (less than 10 minutes) on October 17th (Tuesday).

This is the one that received the agent update the other day (mackerel-agent has been updated with countermeasures for .io domain malfunctions - Mackerel blog #mackerelio). We will continue to support previous domains, but we also ask you to update your agent to minimize the impact of the possible future .io domain failure.

im.kayac service termination and Mackerel support

Service for, one of Mackerel’s notification partners, will end on October 31st, 2017.

By the end of this month, im.kayac will no longer be available as a notification channel for Mackerel. This is the first announcement, a detailed schedule will be announced separately.

API release for Notification channels/Notification groups

We’ve released an API for Notification channels/Notification groups!

By all means, try out automating notification configurations!

Updates for Mackerel related OSS

The following Mackerel related OSS have been updated. A big thank you to everyone who contributed!

mackerel-agent-plugins v0.36.0

  • mackerel-plugin-json added
    • This plug-in accepts standard output in json format and can output as custom metrics.
  • [aws-dynamodb] graph definitions corrected
    • An issue occurred where some metric graphs were displayed with unintended names. This issue was corrected and will become incompatible.
    • The changes are as follows.
    • custom.dynamodb.SystemErrors.SystemErrors.<command> => custom.dynamodb.SystemErrors.<command>
    • custom.dynamodb.SuccessfulRequests.SuccessfulRequests.<command> => custom.dynamodb.SuccessfulRequests.<command>
    • custom.dynamodb.ThrottledRequests.ThrottledRequests.<command> => custom.dynamodb.ThrottledRequests.<command>
    • custom.dynamodb.UserErrors.UserErrors.<command> => custom.dynamodb.UserErrors.<command>
  • [unicorn] metric-key-prefix option added
  • [aws-elasticsearch] The type/content of metrics to be obtained have been improved.

go-check-plugins v0.14.0

  • [check-log] When the return option is specified, the target file name is now output as well.

fluent-plugin-mackerel v1.1.0

Mackerel related events this month

We’ve been holding lots of Mackerel related events recently and we don’t plan on stopping anytime soon!

10/27 (Friday) - Mackerel UG organized・Monitoring workshop

Mackerel UG, a group made up of volunteer Mackerel users, is organizing a monitoring workshop on Friday, October 27th in the offices of LINE! (Japanese only)

Although this event is being hosted by Mackerel UG, there’ll be discussions about other OSS monitoring tools such as Zabbix and Prometheus, so this is a good opportunity to think about server monitoring in general.

10/31 (Tuesday) - Mackerel booth @ AWS CloudRoadShow Fukuoka

Following the event in Nagoya the other day, Mackerel will also be running a booth at the AWS CloudRoadShow Fukuoka!

AWS Cloud Roadshow 2017 福岡 powered by Intel® 広島、大阪、名古屋、福岡の 4 都市を巡る無料クラウドカンファレンス開催! | アマゾン ウェブ サービス (Japanese only)

Come and join us on the last leg of our national tour with the AWS CloudRoadShow!

10/30 (Monday) - Mackerel team CRE to present at Geeks Who Drink in Fukuoka -Monitoring Workshop Edition-!

On the day before the above-mentioned AWS CloudRoadShow Fukuoka, Monday October 30th, Mackerel team CRE・id:Soudai will be presenting at Geeks Who Drink in Fukuoka -Monitoring Workshop Edition- held at the Fukuoka branch offices of Nulab Co., Ltd.! (Japanese only)

At this workshop, you’ll be able to listen to talks on diverse topics such as operation monitoring with Nulab services (Backlog), container monitoring from GMO Pepabo, and more. We still have plenty of room, so please join us if you’re interested!