In IBM Cloud Pak for Integration (CP4I) v2021.2, which runs on Red Hat OpenShift, logging is managed through the OpenShift Logging Operator. This operator is responsible for collecting, storing, and forwarding logs within the cluster.
The OpenShift Logging Operator monitors a specific Custom Resource (CR) named ClusterLogging, which defines the logging stack configuration.
The ClusterLogging CR is used to configure and manage the cluster-wide logging stack, including components like:
Fluentd (Log collection and forwarding)
Elasticsearch (Log storage and indexing)
Kibana (Log visualization)
Administrators define log collection, storage, and forwarding settings using this CR.
How the ClusterLogging Custom Resource Works:Example of a ClusterLogging CR Definition:apiVersion: logging.openshift.io/v1
kind: ClusterLogging
metadata:
name: instance
namespace: openshift-logging
spec:
managementState: Managed
logStore:
type: elasticsearch
retentionPolicy:
application:
maxAge: 7d
collection:
type: fluentd
This configuration sets up an Elasticsearch-based log store with Fluentd as the log collector.
The OpenShift Logging Operator monitors the ClusterLogging CR to manage logging settings.
It defines how logs are collected, stored, and forwarded across the cluster.
IBM Cloud Pak for Integration uses this CR when integrating OpenShift’s logging system.
Why Answer A (ClusterLogging) is Correct?
B. DefaultLogging → Incorrect
There is no such resource named DefaultLogging in OpenShift.
The correct resource is ClusterLogging.
C. ElasticsearchLog → Incorrect
Elasticsearch is the default log store, but it is managed within ClusterLogging, not as a separate CR.
D. LoggingResource → Incorrect
Explanation of Incorrect Answers:
OpenShift Logging Overview
Configuring OpenShift Cluster Logging
IBM Cloud Pak for Integration - Logging and Monitoring
IBM Cloud Pak for Integration (CP4I) v2021.2 Administration References:
