A Redis instance is considered non-compliant if its average connection usage meets or exceeds a specified threshold for at least 8 hours within a given time range. The default time range is the last 7 days. This rule does not apply to cluster instances or instances that are not connected to Cloud Monitor or have no monitoring data. Detection relies on the Cloud Monitor API and consumes the free quota of basic Cloud Monitor. For better detection quality, we recommend that you enable Hybrid Cloud Monitoring. For billing details, see the Cloud Monitor billing documentation.
Threat level
Default threat level: Medium.
You can change the threat level as needed.
Detection logic
-
A Redis instance is considered non-compliant if its average connection usage meets or exceeds a specified threshold for at least 8 hours within a given time range. The default time range is the last 7 days. This rule does not apply to cluster instances or instances that are not connected to Cloud Monitor or have no monitoring data. Detection relies on the Cloud Monitor API and consumes the free quota of basic Cloud Monitor. For better detection quality, we recommend that you enable Hybrid Cloud Monitoring. For billing details, see the Cloud Monitor billing documentation.
Rule details
|
Parameter |
Description |
|
Rule name |
Check for the average connection usage of a Redis instance |
|
Rule identifier |
|
|
Tag |
Redis |
|
Automatic remediation |
Not supported |
|
Rule trigger mechanism |
Periodic execution |
|
Trigger frequency |
24 hours |
|
Supported resource types |
ACS::Redis::DBInstance |
|
Input parameters |
relativeTime (Default: 168) |
Remediation
To remediate non-compliant resources identified by this rule, see Instance type guide and FAQ.