About remote health monitoring with MicroShift
Remote health monitoring is conducted in MicroShift by the collection of telemetry and configuration data about your node that is reported to Red Hat with the Telemeter API. A node that reports Telemetry to Red Hat is considered a connected node.
Telemetry is the term that Red Hat uses to describe the information being sent to Red Hat by the MicroShift Telemeter API. Lightweight attributes are sent from a connected node to Red Hat to monitor the health of a node.
Telemetry provides the following benefits:
-
Enhanced identification and resolution of issues. Events that might seem normal to an end-user can be observed by Red Hat from a broader perspective. Some issues can be more rapidly identified from this point of view and resolved without an end-user needing to open a support case or file a Jira issue.
-
Targeted prioritization of new features and functionality. The data collected provides information about system capabilities and usage characteristics. With this information, Red Hat can focus on developing the new features and functionality that have the greatest impact for our customers.
Telemetry sends a carefully chosen subset of the node monitoring metrics to Red Hat. The Telemeter API fetches the metrics values every hour and uploads the data to Red Hat. This stream of data is used by Red Hat to monitor nodes over time.
This debugging information is available to Red Hat Support and Engineering teams with the same restrictions as accessing data reported through support cases. All connected node information is used by Red Hat to help make MicroShift better.
|
|
MicroShift does not support Prometheus. To view the Telemetry gathered from your node, you must contact Red Hat Support. |