Chapter 6. Enable the Logs tab in the web console

Procedure

1. Install the Cluster Observability Operator.

   The COO installs into the openshift-operators namespace, which already has a pre-existing OperatorGroup. No additional namespace or OperatorGroup configuration is required.

2. Create a UIPlugin CR:

   apiVersion: observability.openshift.io/v1alpha1
   kind: UIPlugin
   metadata:
     name: logging
   spec:
     type: Logging
     logging:
       lokiStack:
         name: logging-loki
       logsLimit: 50
       timeout: 30s
       schema: otel

   metadata.name

   Set the name to logging.

   spec.type

   Set the type to Logging.

   spec.logging.lokiStack.name

   Must match the name of your LokiStack instance.

   spec.logging.schema

   Set to otel, viaq, or select. The default is viaq if no value is specified. When you select select, you can select the mode in the UI when you run a query.

   Note

   The following are known issues for the logging UI plugin (OU-587):

   • The schema feature is only supported in OpenShift Container Platform 4.15 and later. In earlier versions, the logging UI plugin uses only the viaq attribute, ignoring any other values that might be set.
   • Non-administrator users cannot query logs by using the otel attribute with logging versions 5.8 to 6.2. (LOG-6589)

3. Apply the UIPlugin CR by running the following command:

   $ oc apply -f <filename>.yaml

4. Refresh the OpenShift Container Platform web console. Navigate to Observe Logs to verify that the Logs tab is available. You can also view aggregated logs for individual pods from the Aggregated Logs tab on a pod’s detail page.