The Red Hat Advanced Cluster Security for Kubernetes system health dashboard provides a single interface for viewing health related information about Red Hat Advanced Cluster Security for Kubernetes components.
The system health dashboard is only available on Red Hat Advanced Cluster Security for Kubernetes 3.0.53 and newer.
To access the health dashboard:
On the RHACS portal, navigate to Platform Configuration → System Health.
The health dashboard organizes information in the following groups:
Cluster Health - Shows the overall state of Red Hat Advanced Cluster Security for Kubernetes cluster.
Vulnerability Definitions - Shows the last update time of vulnerability definitions.
Image Integrations - Shows the health of all registries that you have integrated.
Notifier Integrations - Shows the health of any notifiers (Slack, email, Jira, or other similar integrations) that you have integrated.
Backup Integrations - Shows the health of any backup providers that you have integrated.
The dashboard lists the following states for different components:
Healthy - The component is functional.
Degraded - The component is partially unhealthy. This state means the cluster is functional, but some components are unhealthy and require attention.
Unhealthy - This component is not healthy and requires immediate attention.
Uninitialized - The component has not yet reported back to Central to have its health assessed. An uninitialized state may sometimes require attention, but often components report back the health status after a few minutes or when the integration is used.
The Cluster Overview shows information about your Red Hat Advanced Cluster Security for Kubernetes cluster health. It reports the health information about the following:
Collector Status - It shows whether the Collector pod that Red Hat Advanced Cluster Security for Kubernetes uses is reporting healthy.
Sensor Status - It shows whether the Sensor pod that Red Hat Advanced Cluster Security for Kubernetes uses is reporting healthy.
Sensor Upgrade - It shows whether the Sensor is running the correct version when compared with Central.
Credential Expiration - It shows if the credentials for Red Hat Advanced Cluster Security for Kubernetes are nearing expiration.
Clusters in the
The Vulnerabilities Definition section shows the last time vulnerability definitions were updated and if the definitions are up to date.
There are 3 integration sections Image Integrations, Notifier Integrations, and Backup Integrations. Similar to the Cluster Health section, these sections list the number of unhealthy integrations if they exist. Otherwise, all integrations report as healthy.
The Integrations section lists the healthy integrations as
RHACS provides product usage data for the number of secured Kubernetes nodes and CPU units for secured clusters based on metrics collected from RHACS sensors. This information can be useful to estimate RHACS consumption data for reporting.
For more information on how CPU units are defined in Kubernetes, see CPU resource units.
OpenShift Container Platform provides its own usage reports; this information is intended for use with self-managed Kubernetes systems.
RHACS provides the following usage data in the web portal and API:
Currently secured CPU units: The number of Kubernetes CPU units used by your RHACS secured clusters, as of the latest metrics collection.
Currently secured node count: The number of Kubernetes nodes secured by RHACS, as of the latest metrics collection.
Maximum secured CPU units: The maximum number of CPU units used by your RHACS secured clusters, as measured hourly and aggregated for the time period defined by the Start date and End date.
Maximum secured node count: The maximum number of Kubernetes nodes secured by RHACS, as measured hourly and aggregated for the time period defined by the Start date and End date.
CPU units observation date: The date on which the maximum secured CPU units data was collected.
Node count observation date: The date on which the maximum secured node count data was collected.
The sensors collect data every 5 minutes, so there can be a short delay in displaying the current data. To view historical data, you must configure the Start date and End date and download the data file. The date range is inclusive and depends on your time zone.
The presented maximum values are computed based on hourly maximums for the requested period. The hourly maximums are available for download in CSV format.
The data shown is not sent to Red Hat or displayed as Prometheus metrics.
In the RHACS portal, navigate to Platform Configuration → System Health.
Click Show product usage.
In the Start date and End date fields, choose the dates for which you want to display data. This range is inclusive and depends on your time zone.
Optional: To download the detailed data, click Download CSV.
You can also obtain this data by using the
ProductUsageService API object. For more information, navigate to Help → API reference in the RHACS portal.
You can generate a diagnostic bundle by using the system health dashboard on the RHACS portal.
To generate a diagnostic bundle, you need
read permission for the
On the RHACS portal, select Platform Configuration → System Health.
On the System Health view header, click Generate Diagnostic Bundle.
For the Filter by clusters drop-down menu, select the clusters for which you want to generate the diagnostic data.
For Filter by starting time, specify the date and time (in UTC format) from which you want to include the diagnostic data.
Click Download Diagnostic Bundle.