Hello. This is Sudo (
id:do-su-0805) from the Mackerel Team CRE. Here are the details of the latest updates.
- Detailed information for each route is now available from the APM's HTTP Server tab
- Added a column to the Notification groups API response to determine if it is the default notification group
- Notification channels are no longer automatically added to the default notification group when created using terraform-provider-mackerel
- Added Kubernetes 1.36 as a supported environment for mackerel-container-agent
- The Open Beta for the Log Feature will be released on July 16th!
Detailed information for each route is now available from the APM's HTTP Server tab
In the APM HTTP Server tab, along with a list of various routes, statistical information such as total/average response times, percentiles, request counts, and error rates, as well as links to the trace list search screen, were displayed.
With this update, clicking on a route name now opens a detailed view for that route.
At the top of the detailed view, statistical information is displayed in a tabular format, and you can monitor the trends of request counts, error counts, and latency through graphs.
By selecting a time period within the graph, you can change the displayed time range. The statistical information will also switch to aggregate data for the selected display range.
Additionally, a list of traces for the relevant route is displayed at the bottom of the detailed view, allowing you to filter by latency or status code (note that filtering does not affect the content displayed in the graphs).
Please note that the link to navigate to the route's trace list screen has been moved to the middle section of the newly added detailed view.
This makes it easier to notice anomalies or changes during routine operational checks and allows you to quickly reach the relevant traces for investigation. We hope you find it useful!
Added a column to the Notification groups API response to determine if it is the default notification group
A type column has been added to the responses of the Register Notification Groups API and Get the notification group list API. The value of the type column will be group-default for the default notification group, and group for other notification groups.
For details, please refer to the "Response" section of the Register Notification Groups API below.
Notification groups - Mackerel API Documents (v0)
Notification channels are no longer automatically added to the default notification group when created using terraform-provider-mackerel
Previously, when a notification channel was created using terraform-provider-mackerel, it was automatically added to the default notification group. We have updated this behavior so that it is no longer automatically added.
Instead, the mackerel_default_notification_group resource is now available, allowing you to manage the default notification group in the same way as regular notification groups. If you want to add a notification channel to the default notification group, please use this resource to do so.
Please note that the mackerel_default_notification_group resource does not support import. When you start using it, you can begin managing the default notification group by writing the resource configuration to match your current settings. Please note that if the configuration does not match the current state, it will be overwritten with the content specified in your configuration.
This change is available starting from terraform-provider-mackerel v0.10.0.
Added Kubernetes 1.36 as a supported environment for mackerel-container-agent
We have added Kubernetes 1.36 as a supported environment for mackerel-container-agent.
Operation has been verified on Amazon EKS. Please note that Windows containers are not supported.
For usage instructions, please refer to the following help documentation.
The Open Beta for the Log Feature will be released on July 16th!
We recently announced that Mackerel's log feature will be released as an open beta on Thursday, July 16, 2026.
In the beta version, you can try out the log search experience ahead of the official release. The feature is designed to empower the entire team to handle logs, allowing you to easily build search conditions on the screen and share or reuse them within your team.
For more details, please check out our pre-announcement article! (in Japanese)
