4.3. Configuring monitoring to use OpenShift Data Foundation

Procedure

1. In the OpenShift Web Console, go to Workloads Config Maps.
2. Set the Project dropdown to openshift-monitoring.
3. Click Create Config Map.

4. Define a new cluster-monitoring-config Config Map using the following example.

   Replace the content in angle brackets (<, >) with your own values, for example, retention: 24h or storage: 40Gi.

   Replace the storageClassName with the storageclass that uses the provisioner openshift-storage.rbd.csi.ceph.com. In the example given below the name of the storageclass is ocs-storagecluster-ceph-rbd.

   Example cluster-monitoring-config Config Map

   apiVersion: v1
   kind: ConfigMap
   metadata:
     name: cluster-monitoring-config
     namespace: openshift-monitoring
   data:
     config.yaml: |
         prometheusK8s:
           retention: <time to retain monitoring files, for example 24h>
           volumeClaimTemplate:
             metadata:
               name: ocs-prometheus-claim
             spec:
               storageClassName: ocs-storagecluster-ceph-rbd
               resources:
                 requests:
                   storage: <size of claim, e.g. 40Gi>
         alertmanagerMain:
           volumeClaimTemplate:
             metadata:
               name: ocs-alertmanager-claim
             spec:
               storageClassName: ocs-storagecluster-ceph-rbd
               resources:
                 requests:
                   storage: <size of claim, e.g. 40Gi>

5. Click Create to save and create the Config Map.

Verification steps

1. Verify that the Persistent Volume Claims are bound to the pods.

   1. Go to Storage Persistent Volume Claims.
   2. Set the Project dropdown to openshift-monitoring.

   3. Verify that 5 Persistent Volume Claims are visible with a state of Bound, attached to three alertmanager-main-* pods, and two prometheus-k8s-* pods.

      그림 4.1. Monitoring storage created and bound

      

2. Verify that the new alertmanager-main-* pods appear with a state of Running.

   1. Go to Workloads Pods.
   2. Click the new alertmanager-main-* pods to view the pod details.

   3. Scroll down to Volumes and verify that the volume has a Type, ocs-alertmanager-claim that matches one of your new Persistent Volume Claims, for example, ocs-alertmanager-claim-alertmanager-main-0.

      그림 4.2. Persistent Volume Claims attached to alertmanager-main-* pod

      

3. Verify that the new prometheus-k8s-* pods appear with a state of Running.

   1. Click the new prometheus-k8s-* pods to view the pod details.

   2. Scroll down to Volumes and verify that the volume has a Type, ocs-prometheus-claim that matches one of your new Persistent Volume Claims, for example, ocs-prometheus-claim-prometheus-k8s-0.

      그림 4.3. Persistent Volume Claims attached to prometheus-k8s-* pod