Skip to content

Commit 66ad943

Browse files
committed
Rename sample directory and enhance description
1 parent 429cb53 commit 66ad943

File tree

4 files changed

+12
-5
lines changed

4 files changed

+12
-5
lines changed

openshift/README.md renamed to cp4i/README.md

Lines changed: 12 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,8 +1,15 @@
1-
# Monitoring metrics in Red Hat OpenShift
2-
This directory contains sample files that demonstrate how to deploy the Prometheus
3-
monitor to gather metrics in a Red Hat OpenShift / Cloud Pak for Integration deployment.
1+
# Monitoring metrics in Cloud Pak for Integration
2+
This directory contains sample files that show how to deploy the Prometheus
3+
monitor to expose queue metrics for a queue manager running in a Cloud Pak for
4+
Integration deployment on Red Hat OpenShift.
45

5-
The basic steps to do this are as follows;
6+
The MQ Certified Container that comes in the Cloud Pak for Integration
7+
emits a range of [queue manager (server) scope metrics](https://www.ibm.com/docs/en/ibm-mq/9.2?topic=containers-metrics-published-by-mq-certified) but does not currently offer an option to
8+
publish information about queues or topics, so use of an additional Prometheus monitor pod as
9+
shown below allows queue (and topic) metrics to be published to Prometheus for consumption
10+
by OpenShift monitoring tools.
11+
12+
The steps to do this are as follows;
613

714
```
815
# Build the Prometheus monitor container as normal
@@ -34,7 +41,7 @@ oc create secret generic metrics-credentials \
3441
3542
3643
# Use the samples in this directory to deploy the Prometheus container to OpenShift
37-
cd mq-metric-samples/openshift
44+
cd mq-metric-samples/cp4i
3845
3946
# Create a new ServiceAccount that will ensure the metrics pod is
4047
# deployed using the most secure Restricted SCC
File renamed without changes.
File renamed without changes.
File renamed without changes.

0 commit comments

Comments
 (0)