Monitoring when using the IBM MQ Operator

Queue managers managed by the IBM® MQ Operator can produce metrics compatible with Prometheus. Queue manager metrics are enabled and served through HTTP by default.

Before you begin

Using HTTPS for queue manager metrics

From 9.4.2.0-r1, queue managers can serve metrics through HTTPS using an OpenShift® created certificate. Prior to 9.4.2.0-r1 queue managers can only serve metrics through HTTP.

Note: All queue managers serve metrics through HTTP by default.

About this task

Prometheus is an open source time-series database and a rule evaluation engine for metrics. The IBM MQ containers expose a metrics endpoint that can be queried by Prometheus. The metrics are generated from the IBM MQ Operator system topics for monitoring and activity trace.

OpenShift Container Platform includes a pre-configured, pre-installed, and self-updating monitoring stack that uses a Prometheus server. The OpenShift Container Platform monitoring stack needs to be configured to monitor user-defined projects. See Enabling monitoring for user-defined projects.

When you create a QueueManager with metrics enabled, the IBM MQ Operator creates a ServiceMonitor that the Prometheus Operator can then discover.

Procedure

View queue manager metrics using the Red Hat OpenShift Container Platform (OCP) monitoring stack.
1. Open the Metrics tab in OCP.
2. Click Observe > Metrics.
Serve queue manager metrics through HTTPS
Set .spec.queueManager.metrics.tls.provider to openshift.
```
spec:
  queueManager:
    metrics:
      enabled: true
      tls:
        provider: openshift
```
Note:
Using this setting creates an OpenShift certificate that is used by the HTTPS metrics server of a queue manager. No other providers can be configured for use by the IBM MQ Operator.
Disable queue manager metrics.

Set .spec.queueManager.metrics.enabled to false.