Attribute information in trace details is now tabbed and searchable, plus 4 other updates

Hello! This is Sudo (id:do-su-0805) from the Mackerel CRE team. Here are the details of our latest update.

Attributes in trace details are now tabbed and searchable

You can check span attributes in the APM trace details screen. To improve the visibility of this attribute information, we've made some changes so that it will be shown it in multiple tabs, organized by category, such as "Status" and "Resource."

Tabbed display of span attributes

We've also added a search function for attribute names and values, making it possible to quickly find the desired attribute information. If a search returns a hit, a blue dot will appear on the tab, allowing you to easily see that it contains relevant information.

Only results of search are displayed

Even if search returns no hits for current tab, blue dots indicate hits in other tabs

Our Custom Dashboard Auto-Generation feature for custom dashboards now supports ECS clusters

Our Custom Dashboard Auto-Generation feature for custom dashboards now supports ECS clusters registered via AWS integration. When a three-tier template is being used, if an ECS cluster is registered in a role specified as a web or app role, graphs of task counts and service CPU and memory utilization will be created.

Example graphs inserted upon specification of role that includes ECS cluster

The list of keyboard shortcuts has been revised

Mackerel provides keyboard shortcuts for a more convenient user experience. You can show a list of available shortcuts by pressing the ? key on the screen.

List of shortcuts viewable by pushing '?' key

We recently corrected some errors in this list. It now shows the correct information. We hope you'll try out some shortcuts to get more convenience out of your Mackerel experience.

Fixed a bug in terraform-provider-mackerel where the provider settings were not used if environment variables were not set

terraform-provider-mackerel allows you to specify an api_key for communicating with Mackerel and, if necessary, an api_base to communicate with. These can be set using environment variables or provider arguments.

The intended behavior was for environment variables to take precedence, and if no environment variables were set, to use the settings specified for the provider. However, there was a bug in these controls making the values specified for the provider unusable.

This bug has been fixed so that the intended order of precedence (environment variables > provider settings) is used correctly.

@mkusaka reported this issue and contributed the fix. Thank you, mkusaka!

[Notice] The Typetalk notification channel will be discontinued on December 1st, 2025

Due to the termination of the Typetalk service scheduled for December 1st, 2025, the Typetalk notification channel will likewise be discontinued as of December 1st, 2025.

We apologize for any inconvenience this may cause to users, and we appreciate your kind understanding.