Enabling and using logging

You can access the logs for running pods, which are available in the OpenShift web console, without installing a logging solution. However, these logs are not saved when a pod stops running or is deleted. To make logging data persistent, you need to need to install a logging solution for your OpenShift cluster.

If you want to persist logging data, follow the instructions to install the Loki Operator Installing logging in the Red Hat OpenShift documentation.

Visualization for logging is provided by the Logging UI Plugin of the OpenShift Cluster Observability Operator.

Configuring the Logging UI Plugin allow users of both the OpenShift web console and the IBM Cloud Pak Platform UI to visualize the logs for instances.

Complete the following steps in the {rhos] documentation:

1. Installing the Cluster Observability Operator (if you have not done so already)

2. Installing the Logging UI Plugin, in Logging UI plugin.

The Platform UI includes menu options to seamlessly access filtered, customized views provided by the OpenShift Logging UI Plugin. To navigate to the log filters, follow these steps:

1. Log in to the IBM Cloud Pak Platform UI.

2. In the list of instances, find the desired instance.

3. Click the overflow menu (three-dot icon), then click Logs.

A new tab opens with the logs of all the pods that are part of the respective instance.

Create an OpenShift cluster log forwarder so that you can forward logs to a third-party application. For instructions, see Configuring log forwarding in the Red Hat OpenShift documentation.

If you are forwarding logs to an external log store and using an external UI instead of the Logging UI Plugin, add and configure the loggingUrl parameter of the PlatformNavigator Kubernetes resource. This configuration links the Platform UI to the external logging UI.

spec:
  loggingUrl: "https://external.ui.url.com"

When the configuration is successful, click Logs in the overflow menu (three-dot icon) for a given instance to navigate to the specified URL.

Auditing logs is useful for monitoring user operations within your IBM Cloud Pak for Integration deployment, such as create, read, update, delete, login, and logout activity.

The logs for users actions in the Platform UI are in the services container in the Platform UI pod. These logs are assigned a unique prefix ([USER-LOG]) so they can be captured and audited.

For more information about available audit logging for instances, see the following documentation:

• API management

• Enterprise gateway

• Event Manager

• Integration dashboard

• Kafka cluster

• Queue manager