Idle check for MongoDB instance disk usage

更新时间:
复制 MD 格式

Checks whether a MongoDB instance's maximum disk usage reaches a specified threshold within a given period (default: 7 days). Does not apply to instances unmonitored by CloudMonitor, without monitoring data, or that are not multi-node cluster instances. This check consumes the Basic CloudMonitor free quota. For better detection quality, enable Hybrid Cloud Monitoring.

Risk level

Default risk level: Low.

You can change the risk level based on your requirements.

Detection logic

  • A MongoDB instance is considered compliant if its maximum disk usage is greater than or equal to a set value during a specific period.

  • This rule does not apply if a MongoDB instance is not monitored by CloudMonitor, has no monitoring data, or is not a multi-node cluster instance.

The default check period is 7 days. This check uses CloudMonitor APIs and consumes the Basic CloudMonitor free quota. To ensure detection quality, enable Hybrid Cloud Monitoring. For Hybrid Cloud Monitoring billing, see CloudMonitor billing details.

Rule details

Parameter

Description

Rule name

Idle check for MongoDB instance disk usage

Rule identifier

mongodb-disk-max-utilization-check

Tag

[MongoDB]

Automatic remediation

Not supported

Rule trigger

Period: 24 hours

Supported resource types

[ACS::MongoDB::DBInstance]

Input parameters

relativeTime(default value: 168)
utilization(default value: 10)

Remediation guide

For remediation steps, see Instance specifications.