OpenShift Container Platform provides various resources for monitoring at the cluster level.

About OpenShift Container Platform cluster monitoring

OpenShift Container Platform includes a pre-configured, pre-installed, and self-updating monitoring stack that is based on the Prometheus open source project and its wider eco-system. It provides monitoring of cluster components and includes a set of alerts to immediately notify the cluster administrator about any occurring problems and a set of Grafana dashboards. The cluster monitoring stack is only supported for monitoring OpenShift Container Platform clusters.

To ensure compatibility with future OpenShift Container Platform updates, configuring only the specified monitoring stack options is supported.

About cluster logging

The cluster logging components are based upon Elasticsearch, Fluentd, and Kibana (EFK). The collector, Fluentd, is deployed to each node in the OpenShift Container Platform cluster. It collects all node and container logs and writes them to Elasticsearch (ES). Kibana is the centralized, web UI where users and administrators can create rich visualizations and dashboards with the aggregated data.

For more information on cluster logging, see the OpenShift Container Platform cluster logging documentation.

About Telemetry

Telemetry collects anonymized aggregated information about:

  • The size of an OpenShift Container Platform cluster

  • The health and status of OpenShift Container Platform components

  • Use of OpenShift Container Platform components

  • The features in use

This information is used by Red Hat to help make OpenShift Container Platform better and more intuitive to use. None of the information is shared with third parties.

What information is collected

Telemetry does not collect, and will never collect, identifying information like user names, passwords, or the names or addresses of user resources.

Primary information collected includes:

  • Number of updates available per cluster

  • Channel and image repository used for an update

  • Number of errors that occurred during an update

  • Progress information of an update that is running

  • Number of machines per cluster

  • Number of CPU cores and size of RAM of the machines

  • Number of members in the etcd cluster and number of objects currently stored in the etcd cluster

  • Number of CPU cores and RAM used per machine type - infra or master

  • Number of CPU cores and RAM used per cluster

  • Use of OpenShift Container Platform framework components per cluster

  • Version of the OpenShift Container Platform cluster

  • Health, condition, and status for any OpenShift Container Platform framework component that is installed on the cluster, for example Cluster Version Operator, Cluster Monitoring, Image Registry, and Elasticsearch for Logging

  • A unique random identifier that is generated during installation

  • Name of the platform OpenShift Container Platform is deployed on, such as Amazon Web Services

CLI troubleshooting and debugging commands

For a list of the oc client troubleshooting and debugging commands, see the OpenShift Container Platform CLI reference documentation.