A MongoDB instance is compliant if its maximum CPU utilization over a specified period meets or exceeds a set threshold. The rule does not apply to instances that are not monitored by CloudMonitor, have no monitoring data, or are not multi-node cluster deployments. The default check period is the last 7 days. This check retrieves monitoring data through the CloudMonitor API and consumes your basic CloudMonitor free quota. To improve check quality, enable Hybrid Cloud Monitoring. For billing details, see CloudMonitor billing.
Risk level
Default risk level: Low.
You can change the risk level based on your requirements.
Detection logic
-
A MongoDB instance is compliant if its maximum CPU utilization over a specified period meets or exceeds a set threshold.
-
The rule does not apply if the instance is not monitored by CloudMonitor, has no monitoring data, or is not a multi-node cluster deployment.
The default check period is the last 7 days. This check retrieves monitoring data through the CloudMonitor API and consumes your basic CloudMonitor free quota. To improve check quality, enable Hybrid Cloud Monitoring. For billing details, see CloudMonitor billing.
Rule details
|
Parameter |
Description |
|
Rule name |
Idle check for MongoDB instance CPU utilization |
|
Rule identifier |
|
|
Tag |
[MongoDB] |
|
Automatic remediation |
Not supported |
|
Rule trigger |
24-hour period |
|
Supported resource types |
[ACS::MongoDB::DBInstance] |
|
Input parameters |
relativeTime(Default value: 168) |
Remediation guide
For remediation steps, see Instance type.