OpenShift Logging Explained¶

Introduction¶

OpenShift logging depends on collectors, storage, and log query components. Troubleshoot by checking collector DaemonSets, namespace events, and whether logs are reaching the backend.

Core Concepts¶

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

Practical Examples¶

oc get pods -n openshift-logging

oc logs daemonset/collector -n openshift-logging --tail=50

oc get events -n openshift-logging --sort-by=.lastTimestamp

oc adm top pods -n openshift-logging

Example output:

NAME                        READY   STATUS    RESTARTS   AGE
collector-7k9xm              1/1     Running   0          3d
log-storage-0                1/1     Running   0          3d

Verification¶

oc get pods -n openshift-logging

oc logs daemonset/collector -n openshift-logging --tail=50

Common Mistakes¶

• Assuming application logs are missing before checking collector health.
• Ignoring storage pressure in the logging backend.
• Collecting logs from the wrong namespace.

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 Logging Explained is best understood through the OpenShift objects involved and the oc commands that verify their current state.