Apache ActiveMQ OpenTelemetry Assets

Apache ActiveMQ (Classic) is an open-source, Java-based message broker implementing the Java Message Service (JMS) API. It acts as an intermediary for asynchronous communication between distributed applications, decoupling producers from consumers.

This content pack provides pre-built dashboards, alert rules, and SLO templates that visualize and alert on Apache ActiveMQ JMX metrics collected using the OpenTelemetry JMX Scraper, covering broker health, capacity, message flow, destinations, and error signals.

The Apache ActiveMQ OpenTelemetry assets have been tested with the OpenTelemetry JMX Scraper v1.53.0 (otel.jmx.target.system=activemq) and OpenTelemetry Collector Contrib v0.145.0. Apache ActiveMQ (Classic) tested against versions 5.x and 6.x.

You need Elasticsearch for storing and searching your data and Kibana for visualizing and managing it. You can use our hosted Elasticsearch Service on Elastic Cloud, which is recommended, or self-manage the Elastic Stack on your own hardware.

You also need the OpenTelemetry JMX Scraper JAR and an OpenTelemetry Collector (or EDOT Collector) to receive metrics using OTLP and export them to Elasticsearch.

Enable JMX on the ActiveMQ broker so the JMX Scraper can connect and collect metrics. Set the following JVM options (for example in ACTIVEMQ_SUNJMX_START or your startup script):

-Dcom.sun.management.jmxremote
-Dcom.sun.management.jmxremote.port=1099
-Dcom.sun.management.jmxremote.rmi.port=1099
-Dcom.sun.management.jmxremote.ssl=false
-Dcom.sun.management.jmxremote.authenticate=true
-Dcom.sun.management.jmxremote.password.file=${ACTIVEMQ_CONF}/jmxremote.password
-Dcom.sun.management.jmxremote.access.file=${ACTIVEMQ_CONF}/jmxremote.access
		

Create jmxremote.password and jmxremote.access files with appropriate permissions.

The JMX Scraper runs as a standalone Java process that connects to ActiveMQ's JMX endpoint and exports metrics using OTLP to your collector. Download the latest release and run it with the following configuration:

java -jar opentelemetry-jmx-scraper.jar \
  -config \
  otel.jmx.service.url=service:jmx:rmi:///jndi/rmi://<ACTIVEMQ_HOST>:<JMX_PORT>/jmxrmi \
  otel.jmx.target.system=activemq \
  otel.jmx.username=<JMX_USERNAME> \
  otel.jmx.password=<JMX_PASSWORD> \
  otel.metric.export.interval=30s \
  otel.exporter.otlp.endpoint=http://<COLLECTOR_HOST>:4317
		

You can also configure the scraper using environment variables (for example OTEL_JMX_SERVICE_URL, OTEL_JMX_TARGET_SYSTEM) or a properties file. refer the JMX Scraper documentation for the full configuration reference.

Configure your OpenTelemetry Collector or EDOT Collector to receive the OTLP metrics from the JMX Scraper and export them to Elasticsearch:

receivers:
  otlp:
    protocols:
      grpc:
        endpoint: 0.0.0.0:4317

processors:
  batch:
    timeout: 10s
    send_batch_size: 200
  resource:
    attributes:
      - key: data_stream.dataset
        value: activemq
        action: upsert

exporters:
  elasticsearch/otel:
    endpoints: [<ES_ENDPOINT>]
    api_key: ${env:ES_API_KEY}
    mapping:
      mode: otel

service:
  pipelines:
    metrics:
      receivers: [otlp]
      processors: [batch, resource]
      exporters: [elasticsearch/otel]
		

Refer to the JMX Scraper and the ActiveMQ metrics definitions for details on available metrics. Data is written to the metrics-activemq.otel-* index pattern.

This integration includes one or more Kibana dashboards that visualizes the data collected by the integration. The screenshots below illustrate how the ingested data is displayed.

← →

×

×

×