The OpenTelemetry Collector, when configured with a Prometheus receiver, provides an integration with IBM MQ to ingest metrics. The Collector fetches metrics from the configured path in the IBM MQ configuration file and sends it to the Prometheus exporter. From there the metrics are received and processed by the Prometheus receiver and exported to Cloud Observability.
To complete the integration, you will:
You need to configure IBM MQ to use the Prometheus exporter.
The port for IBM MQ Prometheus monitoring (
9157 by default) can be toggled with the environmental variable:
For more details about using IBM MQ with the Prometheus exporter, see the official IBM MQ documentation.
In the Collector configuration file, configure the Prometheus receiver to use the IBM MQ endpoint as a scrape target.
- job_name: 'ibmq-scraper'
- targets: [":9157"]
targets field must be the same as the default port for IBM MQ
The OpenTelemetry repo’s readme provides additional details about Prometheus receiver configuration.
Once the IBM MQ 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 Organization settings.
In Cloud Observability, click Organization settings > Metric details.
Search for IBM MQ metric names.
If needed, click on the metric to edit the description and how the units are displayed in Cloud Observability.
Use the Cloud Observability Terraform Provider to create a dashboard for the metrics.
For a more complete example that’s ready to run, see the IBM MQ integration in Cloud Observability OpenTelemetry Examples.
Updated Dec 1, 2022