AWS Integration for Amazon Connect Now Supports Host Filtering by Tags, and more

Hello, this is Mackerel team CRE id:masarasi. I'm pleased to share the details of this update.

AWS Integration for Amazon Connect Now Supports Host Filtering by Tags

In the Amazon Connect integration of the AWS Integration, you can now use the feature to specify tags to filter hosts to register.

In your Amazon Connect environment, you can now integrate only the targets you want to monitor into Mackerel, which reduces unnecessary host fees.

Notification Channel Registration API Now Allows Choosing Whether to Add to the Default Notification Group

Previously, notification channels created via the Register Notification Channel were forcibly added to the default notification group. If you didn't want them added to the default notification group, you had to manually remove them from the default group's notification destinations after registering the channel, which was a hassle.

With this update, you can now use the addToDefaultNotificationGroup parameter to specify whether or not to add the channel to the default notification group when registering a notification channel.

Check Monitoring Candidates for Notification Groups Will No Longer Display Items with No Recent Submissions

Previously, the list of monitoring rules to be specified as notification targets for a notification group displayed all check monitors registered within the organization. As a result, old check monitors of retired hosts were also displayed, making it difficult to distinguish which check monitors were currently active.

With this change, check monitors that have not posted for a while (30 days or more) will no longer be displayed as candidates, making it easier to select your target check monitors.

Improved Display Speed for Metric Explorer

Previously, the Metric Explorer automatically executed a search every time the screen was opened, which could cause the screen to take some time to display.

With this change, the search is no longer executed automatically when the screen is opened, improving the display speed. Consequently, graphs will no longer be displayed simply by opening the screen. To display graphs, please specify the criteria and click the search button.

Initial state of Metric Explorer

Changed the Design of Slack Notifications

As previously announced in the April Newsletter, we have changed the appearance of Slack notifications. This change makes it easier to grasp the necessary information from the Slack notification content.

Example of the new Slack notification screen

Note: If the Notification Destination for a Slack Channel is Set to a Non-Slack URL

Due to this change, a temporary issue occurred where notifications failed when a non-Slack URL (such as Discord or Mattermost) was configured as the notification destination for a Slack channel. This issue has now been resolved.

Please note that notifications to non-Slack destinations using Slack channels are outside the scope of operation guarantees. Since we do not guarantee future compatibility, please keep this in mind if you are using such configurations.

Mackerel Web Console and API Endpoints Now Support IPv6

As previously announced in Important: IPv6 Support for Mackerel Web Console and API Endpoints, and Associated Action Required for "IP restriction" Settings, the Mackerel Web Console, API endpoints, and other services have been accessible via IPv6 starting Thursday, May 21st.

As mentioned in the advance notice, if you use the "IP Restrictions" feature and use IPv6 communication to connect to the internet, please configure the permission settings for the source IPv6 addresses (or network ranges).

The IPv6 ranges on the Mackerel side are published on the following page:

• What is Mackerel's IP address and port number?

Other Improvements

• Fixed an issue in the AWS Integration settings screen where the number of ECS Clusters was incorrectly displayed as the number of Lambda functions in the "Current connected hosts" count.

Notice: OK Notifications Will Be Sent When Alerts Are Closed Due to Host Retirement

Currently, when a host is retired, alerts that were open on that host are automatically closed, but OK notifications are not sent at that time.

In an upcoming update, OK notifications will also be sent when alerts are closed due to retirement. This will allow you to confirm via notification that an alert was closed due to retirement.

Please be aware that this specification change may result in an increased number of notifications compared to before.