Cluster logging

A logging service is not offered with an IBM® App Connect Operator installation, so if you need to persist logging data, you must implement a logging solution if you do not already have a logging stack that collects and stores logs for your cluster.

Deploying a logging stack

Ensure that you have cluster administrator authority with cluster-admin permissions.

Before you upgrade to the latest version of the IBM App Connect Operator, ensure that one of these logging alternatives is implemented for your cluster:

OpenShift® cluster logging

You can use OpenShift cluster logging to aggregate and store the logs from your cluster into a log store. OpenShift provides Operators that can be installed and used to deploy the components to collect, store, and visualize infrastructure logs, application logs, and audit logs.

If OpenShift cluster logging is deployed, App Connect automatically detects it and forwards logs to the log store. For more information, see About Logging and Installing Logging in the OpenShift documentation.

Custom logging

You can use a custom logging stack if preferred. For information about forwarding logs to other log aggregators, see About log collection and forwarding in the OpenShift documentation.

Tip: If you are using App Connect as part of an IBM Cloud Pak for Integration deployment, you do not have to separately deploy cluster logging because the centralized logging solution for IBM Cloud Pak for Integration will apply.

Viewing cluster logs

For information about viewing logs, see Viewing cluster logs in Red Hat OpenShift.