Checks whether the CloudMonitor agent is installed and runs as expected on all nodes in each Container Service for Kubernetes (ACK) cluster.
Scenario
When you create, modify, or delete an application that is deployed on a node in an ACK cluster, the CloudMonitor agent automatically synchronizes the metadata of the application to CloudMonitor. This allows you to monitor the containers of the application and receive alerts when exceptions occur in the application.
Risk level
Default risk level: high.
You can change the risk level as required when you apply this rule.
Compliance evaluation logic
- If the CloudMonitor agent is installed and runs as expected on all nodes in each ACK cluster, the evaluation result is compliant.
- If the CloudMonitor agent is not installed on a node in an ACK cluster or the CloudMonitor agent does not run as expected on a node, the evaluation result is non-compliant. For more information about how to correct the non-compliant configuration, see Non-compliance remediation.
Rule details
| Item | Description |
|---|---|
| Rule name | ack-cluster-node-monitorenabled |
| Rule ID | ack-cluster-node-monitorenabled |
| Tag | ACK and CMS |
| Automatic remediation | Not supported |
| Trigger type | Periodic execution |
| Time interval | 24 hours |
| Supported resource type | ACK cluster |
| Input parameter | None |
Non-compliance remediation
Install the CloudMonitor agent on all nodes in the ACK cluster and make sure that the CloudMonitor agent runs as expected. For more information about how to manage alerts in an ACK cluster, see Alert management.