1.4. Migrating logging visualization

Procedure

1. Install the Cluster Observability Operator. For more information, see Installing the Cluster Observability Operator.
2. Navigate to the Installed Operators page. Under Provided APIs, select ClusterObservabilityOperator. Find the UIPlugin resource and click Create Instance.

3. Select the YAML view, and then use the following template to create a UIPlugin custom resource (CR):

   Example UIPlugin CR

   apiVersion: observability.openshift.io/v1alpha1
   kind: UIPlugin
   metadata:
     name: logging  

   1

   
   spec:
     type: Logging  

   2

   
     logging:
       lokiStack:
         name: logging-loki  

   3

   
       logsLimit: 50
       timeout: 30s
       schema: otel 

   4

   1

   Set name to logging.

   2

   Set type to Logging.

   3

   The name value must match the name of your LokiStack instance. If you did not install LokiStack in the openshift-logging namespace, set the LokiStack namespace under the lokiStack configuration.

   4

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

   注記

   These are the known issues for the logging UI plugin - for more information, see OU-587.

   • The schema feature is only supported in OpenShift Container Platform 4.15 and later. In earlier versions of OpenShift Container Platform, the logging UI plugin will only use the viaq attribute, ignoring any other values that might be set.
   • Non-administrator users cannot query logs using the otel attribute with logging for Red Hat OpenShift versions 5.8 to 6.2. This issue will be fixed in a future logging release. (LOG-6589)
   • In logging for Red Hat OpenShift version 5.9, the severity_text Otel attribute is not set.
4. Click Create.

Verification

1. Refresh the page when a pop-up message instructs you to do so.
2. Navigate to the Observe Logs panel, where you can run LogQL queries. You can also query logs for individual pods from the Aggregated Logs tab of a specific pod.