The OpenTelemetry Collector provides an integration with JMX and ActiveMQ to ingest metrics. The Collector fetches ActiveMQ metrics from JMX. From there the metrics are processed and exported to Cloud Observability.
To complete the integration, you will:
opentelemetry-jmx-metrics.jar
file.The ActiveMQ JMX receiver periodically fetches metrics using a built-in OpenTelemetry helper utilizing a Groovy script. The script is configured to poll both the JMX Agent and the OpenTelemetry JMX Metric Gatherer operation.
For more details regarding configuring the ActiveMQ remote connection, see the official ActiveMQ documentation.
In the Collector configuration file, add JVM and ActiveMQ as a receiver and set the following:
jar_path
: The path to the opentelemetry-jmx-metrics.jar
file.endpoint
: The hostname/IP address and port or unix socket file path of the ActiveMQ instancetarget_system
: The metrics to collect. Valid values for this integration are jvm
and activemq
1
2
3
4
5
receivers:
jmx:
jar_path: /opt/opentelemetry-jmx-metrics.jar
endpoint: "localhost:9999"
target_system: jvm,activemq
The OpenTelemetry repo provides additional details about JMX configuration.
Once the ActiveMQ receiver is configured, enable it by adding it to one or more pipelines as described in the Collector configuration documentation.
You can validate that metrics are reporting to Cloud Observability on the Metrics details page in Settings.
In Cloud Observability, click Settings > Metric details.
Search for ActiveMQ metric names.
If needed, click on the metric to edit the description and how the units are displayed in Cloud Observability.
You can create a pre-built dashboard for this integration from the Dashboard list view. Or use the Cloud Observability Terraform Provider to create a dashboard.
Updated Dec 1, 2022