Alarm Rules Are Enabled
Rule Details
Parameter |
Description |
---|---|
Rule Name |
alarm-action-enabled-check |
Identifier |
Alarm Rules Are Enabled |
Description |
If Cloud Eye alarm rules are not enabled, the check result is non-compliant. |
Tag |
ces |
Trigger Type |
Configuration change |
Filter Type |
ces.alarms |
Rule Parameters |
None |
Application Scenarios
You can set alarm rules for key metrics of cloud services. When the conditions in the alarm rule are met, Cloud Eye sends email, or text message, or sends HTTP/HTTPS messages, enabling you to quickly respond to resource changes. For details, see Alarm Overview.
If an alarm rule is disabled, the resource health status cannot be monitored in real time.
- Key metric monitoring: You can create alarm rules to monitor key metrics of core resources, such as the CPU, memory, disk, network traffic, and number of connections of ECSs, RDS DB instances, ELB load balancers, and OBS buckets.
- Anomaly detection: You can detect resource overload, performance bottlenecks, and abnormal fluctuations (for example, the CPU usage is 100% for a long time, the disk is full, or packet loss occurs due to network congestion) in a timely manner, preventing service interruption caused by insufficient resources.
Solution
Rule Logic
- If Cloud Eye alarm rules are not enabled, the check result is non-compliant.
- If Cloud Eye alarm rules are enabled, the check result is compliant.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot