The Notification Channel API Now Supports Updating Settings, and more

Hello! This is Igarashi (id:masarasi) from the Mackerel Team CRE. Here are the details of this update.

The Notification Channel API Now Supports Updating Settings
An API to Retrieve Traces as a List Has Been Released
Trace Search and More Are Now Available with the Mackerel MCP Server
You Can Now Configure the Hostname Listened to by the OTLP Receiver of the Mackerel OpenTelemetry Collector via an Environment Variable
Events Are Now Displayed on the Amazon ElastiCache Host Details Screen
The Mackerel Advent Calendar 2025 Is Now Underway!
Notice of Support Desk Closure During the Year-End and New Year Holidays

The Notification Channel API Now Supports Updating Settings

Previously, the Notification Channel API did not support updating settings, but with this update, it is now possible to update settings as well.

Since updates can be made without accessing the web console, this is useful, for example, when changing the settings of multiple channels, as it helps reduce configuration effort and prevent oversights. At present, only three channels are supported: email notifications, Slack, and Webhooks.

An upcoming release of terraform-provider-mackerel will include support for this feature.

mackerel.io

An API to Retrieve Traces as a List Has Been Released

You can now retrieve a list of traces posted to Mackerel using the API. This is useful for searching for traces that match specified conditions. Please refer to the documentation below for details on how to use the API.

mackerel.io

Trace Search and More Are Now Available with the Mackerel MCP Server

With the release of the API for retrieving a list of traces, the Mackerel MCP Server (v0.3.3 and later) can now be used to search traces, as well as retrieve statistical information from HTTP servers and databases. By leveraging AI, you can expect to resolve application issues based on traces, so we encourage you to give it a try.

In addition, a member of the Mackerel development team has published a blog post describing how they used the Mackerel MCP Server to identify service bottlenecks and improve performance. We encourage you to take a look.

tjmtmmnk.hatenablog.com

We have also recently published the following article about the Mackerel MCP Server. If you would like to learn more about its overview and how to use it, please also refer to this article.

mackerel.io

You Can Now Configure the Hostname Listened to by the OTLP Receiver of the Mackerel OpenTelemetry Collector via an Environment Variable

We recently released the Mackerel OpenTelemetry Collector However, because the hostname used by the OTLP Receiver was fixed to localhost, there was an issue where applications could not communicate with the Collector when both were launched at the same time in environments such as Kubernetes or Docker Compose.

With this release, the updated Mackerel OpenTelemetry Collector (v0.4.0 and newer) allows you to set the hostname to an arbitrary value by using the OTELCOL_MACKEREL_HOST environment variable.

Below is an example of a compose.yaml configuration.

services:
  # Application container
  app:
    ...
    environment:
      # Specify the otelcol-mackerel service name as the hostname
      - OTEL_EXPORTER_OTLP_ENDPOINT=http://otelcol-mackerel:4317
      - OTEL_EXPORTER_OTLP_PROTOCOL=grpc
      - OTEL_EXPORTER_OTLP_INSECURE=true

  # Mackerel OpenTelemetry Collector
  otelcol-mackerel:
    image: mackerel/otelcol-mackerel:0.4.0
    environment:
      # Specify the service name as the hostname
      - OTELCOL_MACKEREL_HOST=otelcol-mackerel
      - MACKEREL_APIKEY

Events Are Now Displayed on the Amazon ElastiCache Host Details Screen

Recent events related to ElastiCache are now displayed on the ElastiCache host details screen. Please note that while these events are retrieved from AWS resource metadata, they cannot be targeted for log monitoring.