Chapter 4. Remote health monitoring
OpenShift Container Storage collects anonymized aggregated information about the health, usage, and size of clusters and reports it to Red Hat via an integrated component called Telemetry. This information allows Red Hat to improve OpenShift Container Storage and to react to issues that impact customers more quickly.
A cluster that reports data to Red Hat via Telemetry is considered a connected cluster.
4.1. About Telemetry
Telemetry sends a carefully chosen subset of the cluster monitoring metrics to Red Hat. These metrics are sent continuously and describe:
- The size of an OpenShift Container Storage cluster
- The health and status of OpenShift Container Storage components
- The health and status of any upgrade being performed
- Limited usage information about OpenShift Container Storage components and features
- Summary info about alerts reported by the cluster monitoring component
This continuous stream of data is used by Red Hat to monitor the health of clusters in real time and to react as necessary to problems that impact our customers. It also allows Red Hat to roll out OpenShift Container Storage upgrades to customers so as to minimize service impact and continuously improve the upgrade experience.
This debugging information is available to Red Hat Support and engineering teams with the same restrictions as accessing data reported via support cases. All connected cluster information is used by Red Hat to help make OpenShift Container Storage better and more intuitive to use. None of the information is shared with third parties.
4.2. Information collected by Telemetry
Primary information collected by Telemetry includes:
The size of ceph cluster in bytes :
The amount of ceph cluster storage used in bytes :
Ceph cluster health status :
The total count of osds :
The total number of Persistent Volumes present in RHOCP cluster :
The total iops (reads+writes) value for all the pools in ceph cluster :
The total iops (reads+writes) value in bytes for all the pools in ceph cluster :
The total count of ceph cluster versions running :
The total number of unhealthy noobaa buckets :
The total number of noobaa buckets :
The total number of noobaa objects :
The count of noobaa’s accounts :
The total usage of noobaa’s storage in bytes :
The total amount of storage requested by PVCs from a particular storage provisioner in bytes:
The total amount of storage used by PVCs from a particular storage provisioner in bytes:
Telemetry does not collect identifying information such as user names, passwords, or the names or addresses of user resources. In addition to the telemetry information stated above, NooBaa sends statistical information about accounts, buckets, objects, capacity, nodes, and connectivity health to phonehome.noobaa.com.