mackerel-agent has been updated with countermeasures for .io domain malfunctions

Yesterday we celebrated Mackerel Day, our third year anniversary event marking the official release of Mackerel. (Japanese only)

Thanks to all of you, the event was a huge success that showcased great presentations from a handful of wonderful speakers. We would like to sincerely thank all the presenters and everyone who attended the event. We will soon be posting a separate report on this blog with details from the event.

Anyways, here is this week’s update information.

mackerel-agent has been updated with countermeasures for .io domain malfunctions

In the blog entry linked below, we made an announcement regarding the .io domain malfunction and the corresponding measures taken by Mackerel. However, this week we have updated mackerel-agent with permanent countermeasures.

Specifically, the API request destination from the agent to Mackerel has been changed from to In response to this, the temporary countermeasures taken, such as changing the connectivity monitoring judgment interval, will be returned to its’ original state in sequential order.

To all of the mackerel-agent users out there, please update the agent or add the description apibase = "" to the top line of the configuration file and restart the agent (excluding KCPS version Mackerel).

Updates for Mackerel related OSS

Below is a list of the updated content including updates for mackerel-agent not mentioned above.

mackerel-agent v0.46.0

  • include_pattern exclude_pattern can now be specified.
    • This allows you to filter the metric type sent from the metric plugin.
    • For details, check out this PullRequest.

mackerel-agent-plugins v0.35.0

  • [twemproxy] Changed so that metrics from each server are not obtained by default
    • If the previous behavior is preferred, use the option-enable-each-server-metrics.

mkr v0.21.0

  • The API request destination to Mackerel has been changed from to

mackerel-client-ruby v0.3.0

  • The API request destination to Mackerel has been changed from to
  • customIdentifier is now available in host searches
  • Metadata API supported

It’s now possible to configure in OpsGenie and PagerDuty to not have alerts closed when closed in Mackerel.

As a settings option for the notification channels OpsGenie and PagerDuty, it is now possible to specify whether or not alerts of OpsGenie/PagerDuty will close according to alerts closing in Mackerel. Try using it in accordance with your team’s incident management style.

Notification channels with improper destinations can now be suspended

Notification channels will now be automatically suspended if they fail a certain number of times for reasons such as having an invalid URL configured or if the the notification destination URL was accidentally deleted etc. While suspended, the channel will be displayed as shown below in the notification channel list.

This status can be lifted by clicking “Unsuspend the channel”.

Other updates

  • Metrics were added to Lambda Integration
    • Iterator Age [ms]
    • Iterator Age [ms] per alias
    • Iterator Age [ms] per version
  • The problem where notifications to PagerDuty would fail when the notification message was too long has been fixed.
  • Sharing graphs with the camera button is now maintained even if the display is switched to a stacked graph.