text: Figure 6-5 OpenShift monitoring 
  
  As highlighted in Figure 6-5, at the heart of the monitoring stack sits the OpenShift Container 
  Platform Cluster Monitoring Operator (CMO), which watches over the deployed monitoring 
  components and resources and ensures that these are always up-to-date. 
  
  The Prometheus Operator (PO) creates, configures, and manages Prometheus and 
  Alertmanager instances. It also automatically generates monitoring target configurations 
  based on familiar Kubernetes label queries. 
  
  In addition to Prometheus and Alertmanager, OpenShift Container Platform Monitoring 
  includes node-exporter and kube-state-metrics. Node-exporter is an agent that is deployed 
  on every node to collect metrics about it. The kube-state-metrics exporter agent converts 
  Kubernetes objects to metrics consumable by Prometheus. 
  
  The following targets are monitored as part of the cluster monitoring: 
  
  (cid:2) Prometheus itself 
  (cid:2) Prometheus-Operator 
  (cid:2) cluster-monitoring-operator 
  (cid:2) Alertmanager cluster instances 
  (cid:2) Kubernetes apiserver 
  (cid:2) kubelets (the kubelet embeds cAdvisor for per container metrics) 
  (cid:2) kube-controllers 
  (cid:2) kube-state-metrics 
  (cid:2) node-exporter 
  (cid:2) etcd (if etcd monitoring is enabled) 