If you are not familiar with the oc command, refer to OpenShift - Getting Started with the oc command.
This assumes OpenShift has been configured with a logging subsystem to injest and store log data. Following are a few common logging subsystems.
Sometimes, you will also create a Cluster Logging Custom Resource (CR). The Cluster Logging Custom Resource will spawn pods and other resources needed by the pods so that Loki or Elastic Search can injest and store log data.
For example, let's say you are going to use Loki to injest and store log data. Check out my Loki article for more details. Following is an example of what you might have for your Cluster Logging Custom Resource so that OpenShift knows to use Loki to injest and store log data.
apiVersion: logging.openshift.io/v1
kind: ClusterLogging
metadata:
name: instance
namespace: openshift-logging
spec:
collection:
type: vector
logStore:
lokistack:
name: logging-loki
type: lokistack
visualization:
type: ocp-console
ocpConsole:
logsLimit: 15
managementState: Managed
Did you find this article helpful?
If so, consider buying me a coffee over at 