Announcements

#mackerelio

Part of the incident and maintenance status page will now be displayed in Japanese, and more

Hello! This is Igarashi (id:masarasi) from the Mackerel CRE team. Here are this week's updates.

Part of the incident and maintenance status page will now be displayed in Japanese

Currently, all content on the status page (which shows incident and maintenance information) is in English.

However, since the majority of Mackerel's users are Japanese speakers, we have received feedback that it can be inconvenient to quickly understand the content in English. As a result, we have decided to display some of the status page content in Japanese going forward.

The changes will apply to the title and body of status updates (shown in the red boxes in the image below). Notifications sent to status page subscribers will also reflect this change for the relevant fields.

Changed fields

Other fields such as Incident Status and Components will remain in English. This decision was made because those fields are relatively easy to understand even in English, and to minimize the impact on users who receive webhook notifications and parse the content to integrate with other systems.

This change will take effect on or after Monday, September 7, 2026.

We apologize for any inconvenience this may cause to users who rely on English-language content or to those in English-speaking regions. We appreciate your understanding.

Regarding the English X account (@mackerelio), we will continue to post in English as before.

Added Labeled Metrics to the status page components

We have added Labeled Metrics to the Components section of the status page. Going forward, maintenance and incidents specific to Labeled Metrics will be tracked separately from the existing host metrics and service metrics component (Metrics).

For details on the scope of impact for each component, please refer to the following page:

Empty service.name attribute in traces is now filled with unknown_service

When the service.name attribute of a submitted trace was empty, Mackerel previously defaulted to saving it as unknown.

With this update, for traces submitted after the update, the value unknown_service will be used instead.

mkr traces command now available for retrieving trace information

We have added the mkr traces subcommand to mkr, which allows you to retrieve information for a specified trace ID. Here's how to use it:

Command

mkr traces get <traceId>

Example output

{
    "spans": [
        {
            "traceId": "fb19ed367cb53f0fe2471073f86b5338",
            "spanId": "a5265beaabb47a7d",
            "traceState": "",
            "name": "GET /products",
            "kind": "server",
            "startTime": "2026-08-03T01:27:16.006Z",
            "endTime": "2026-08-03T01:27:16.032Z",
            "attributes": [
                {
                    "key": "http.request.method",
                    "value": {
                        "valueType": "string",
                        "stringValue": "GET"
                    }
                },
    ...

This feature is available from mkr 0.65.0.

Ended support for Amazon Linux 2 in mackerel-agent

As previously announced, we have ended support for Amazon Linux 2 in mackerel-agent.

Environments where the Mackerel agent is already installed will continue to work, but please note that in principle, we will no longer offer support for any issues that may arise.

For the currently supported operating systems, please refer to the following page:

Updates to the Logs feature (β)

OpenTelemetry attributes attached to logs are now displayed

When logs have OpenTelemetry attributes attached, those attributes were previously not shown in the log search results. You can now view them by expanding a log entry.

Before expanding
After expanding

AND search with multiple keywords is now supported

Previously, when multiple keywords were specified in the log search, they were combined into a single keyword for the search. Now, multiple keywords are treated as AND conditions.

  • Previous behavior: Specifying aa, bb, cc would search for the combined keyword aa bb cc
  • New behavior: Specifying aa, bb, cc will perform an AND search matching all of aa, bb, and cc

When specifying structured log (JSON format) keys as filters in the log search, previously a fixed list of keys (such as user_id) was displayed as suggestions. Now, keys that are actually present in your submitted logs will be suggested instead.