Specified Resources Have Certain Metric Attached

Rule Details

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.

You can associate alarm rules to a specified resource type to monitor the resource status 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

Monitor key metrics of cloud services. Then you can handle exceptions in a timely manner.

Rule Logic

• If the specified resource type is attached to any Cloud Eye alarm of the specified metric, the resource is compliant.
• If the specified resource type is not attached to a Cloud Eye alarm of the specified metric, the resource is non-compliant.