OpenShift Monitoring Explained¶

Introduction¶

OpenShift monitoring runs platform Prometheus, Alertmanager, and related components. Start with pod health, then Alertmanager alerts, targets, and storage pressure.

Core Concepts¶

OpenShift builds on Kubernetes with projects, Routes, ImageStreams, Builds, Operators, SCCs, and integrated platform administration.

Practical Examples¶

oc get pods -n openshift-monitoring

oc get routes -n openshift-monitoring

oc adm top pods -n openshift-monitoring

oc logs statefulset/prometheus-k8s -n openshift-monitoring --tail=50

Example output:

NAME                                  READY   STATUS    RESTARTS   AGE
prometheus-k8s-0                      6/6     Running   0          5d
alertmanager-main-0                   6/6     Running   0          5d

Verification¶

oc get pods -n openshift-monitoring

oc get pvc -n openshift-monitoring

oc get events -n openshift-monitoring

Common Mistakes¶

• Deleting monitoring PVCs to clear space.
• Ignoring persistent volume pressure.
• Assuming user workload monitoring is enabled by default in every cluster.

Quick Checklist¶

• Confirm the active project.
• Inspect the exact object named in the error.
• Read recent events.
• Apply one focused fix.
• Verify status after the change.

Related Guides¶

• Openshift Vs Kubernetes
• Openshift Cli oc Explained
• Openshift Projects Vs Namespaces

Summary¶

OpenShift Monitoring Explained is best understood through the OpenShift objects involved and the oc commands that verify their current state.