Announcements

#mackerelio

Traces and logs can now be sent in the OTLP/HTTP JSON format (http/json), and more

Hello! This is Igarashi ( id:masarasi ) from the Mackerel CRE team. Here are the details of our latest updates.

Traces and logs can now be sent in the OTLP/HTTP JSON format (http/json)

Mackerel's endpoints for receiving traces and logs now support the OTLP/HTTP JSON format.

Until now, only the binary Protobuf format (http/protobuf) was supported. To send data from an environment that only supports JSON — such as Cloudflare Workers — you needed a workaround, such as placing an OpenTelemetry Collector in between to convert the format.

With this update, you can now send data to Mackerel directly in JSON format.

On the sending side, please specify http/json as the protocol.

For traces:

OTEL_EXPORTER_OTLP_TRACES_PROTOCOL="http/json"

For logs:

OTEL_EXPORTER_OTLP_LOGS_PROTOCOL="http/json"

mackerel-agent can now communicate without using the proxy specified in environment variables

mackerel-agent refers to the environment variables (HTTP_PROXY / HTTPS_PROXY) even when no proxy (http_proxy / https_proxy) is set in its configuration file. Because of this, it was difficult to keep mackerel-agent from using a proxy in environments where those environment variables are set.

With this update, when you specify direct for http_proxy / https_proxy in the configuration file, the values of the environment variables are no longer referenced. This makes it easy to communicate without using a proxy.

This specification change applies from mackerel-agent v0.87.1.

Points to note when updating mackerel-agent

Previously, setting https_proxy = "direct" allowed you to prevent HTTPS communication from using the proxy specified in http_proxy (since, when https_proxy is omitted, the proxy specified in http_proxy is automatically used for HTTPS communication as well). However, even with this setting in place, a proxy configured in the environment variables was still used. With this update, specifying direct means the environment variables are not referenced and no proxy is used.

If you have specified direct for https_proxy and are relying on the environment variables to use a proxy for HTTPS communication, please set the URL of your proxy server in https_proxy in the configuration file before updating mackerel-agent.

The following help page includes a table showing the relationship between the proxy settings and the proxy that is actually used. Please refer to it as needed.

Bug fixes

  • Fixed a bug in the check-disk plugin where, when -u kb was specified, thresholds were monitored in MB instead of KB. The fixed version is bundled with mackerel-check-plugins v0.53.0 and later.
    • It is scheduled to be bundled with the Windows version of mackerel-agent at a later date.
  • Fixed a bug where, when on_stop was specified in mackerel-agent's host_status setting, the host status was in rare cases not changed to the specified status. This fix applies from mackerel-agent v0.87.1.

Added Logs to the status page components

We have added Logs to the Components section of the status page. For details on the scope of impact for each component, please refer to the following page:

Please note that, since the Log feature is currently provided as a beta version, incidents and maintenance related to the Log feature will be announced on the status page and elsewhere only on or after its general availability on Sunday, November 1, 2026 (JST).