IBM MQ OpenTelemetry Assets

IBM MQ is an enterprise message-oriented middleware that enables applications to communicate reliably by exchanging messages through queues, supporting both point-to-point and publish/subscribe messaging patterns.

These assets provide dashboards, alert rules, and SLO templates for monitoring IBM MQ queue managers using metrics collected via the OpenTelemetry Prometheus receiver scraping the IBM MQ Prometheus exporter. They cover message throughput, transaction health, API error rates, log subsystem performance, filesystem capacity, and compute resource utilization.

The IBM MQ OpenTelemetry assets have been tested with:

• OpenTelemetry prometheusreceiver v0.146.0 from OpenTelemetry Collector Contrib.
• IBM MQ v9.4.5.0

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 must have the IBM MQ Prometheus exporter running and configured to expose queue manager metrics. The exporter listens on a configurable HTTP port (default 9157) and serves Prometheus-formatted metrics at the /metrics endpoint.

Ensure the exporter has connectivity to your IBM MQ queue manager and is configured with the appropriate credentials and queue manager name.

You can use the OpenTelemetry Collector or the Elastic Distribution of the OpenTelemetry Collector (EDOT Collector) to collect IBM MQ metrics and send them to Elasticsearch.

Placeholders used in the configuration below:

• <ES_ENDPOINT>: Your Elasticsearch endpoint (e.g. https://my-deployment.es.us-east-1.aws.elastic.cloud:443)
• <ES_API_KEY>: Your Elasticsearch API key for authentication
• <MQ_EXPORTER_HOST>: Hostname or IP of the IBM MQ Prometheus exporter (e.g. localhost)
• <MQ_EXPORTER_PORT>: Port of the IBM MQ Prometheus exporter (e.g. 9157)

receivers:
  prometheus/ibmmq:
    config:
      scrape_configs:
        - job_name: ibmmq
          scrape_interval: 60s
          metrics_path: /metrics
          params:
            format: [prometheus]
          scheme: http
          static_configs:
            - targets:
                - "<MQ_EXPORTER_HOST>:<MQ_EXPORTER_PORT>"

processors:
  resource/dataset:
    attributes:
      - key: data_stream.dataset
        value: ibmmq
        action: upsert


exporters:
  elasticsearch/otel:
    endpoints:
      - "${env:ES_ENDPOINT}"
    api_key: "${env:ES_API_KEY}"
    mapping:
      mode: otel

service:
  pipelines:
    metrics:
      receivers: [prometheus/ibmmq]
      processors: [resource/dataset]
      exporters: [elasticsearch/otel]
		

Refer to the metadata.yaml of the OpenTelemetry Prometheus receiver for details on available metrics. The specific IBM MQ metrics are published by the IBM MQ Prometheus exporter and use the ibmmq_qmgr_ prefix.

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.

← →

×

×

×

×