What Alarm Status Does Cloud Eye Support?

Alarm, Resolved, Insufficient data, Alarm (triggered), Expired, and Resolved (forcible clear) are supported.

• Alarm: The metric value reached the alarm threshold, and an alarm has been triggered but not cleared for the resource.
• Resolved: The metric value went back to the normal range, and the resource alarm was cleared.
• Insufficient data: No monitoring data has been reported for three consecutive hours, and this is generally because the instance has been deleted or is abnormal.
• Alarm (triggered): The monitored resource has triggered the event configured in the alarm policy. To filter alarm records in this status, you need to set the alarm type to Event and set Status to Alarm in the search box.
• Expired: The original alarm record is invalid or no longer needs to be handled.
  When you perform the following operations, the alarm record status changes from Alarm or Insufficient data to Invalid:

  • Deleting an alarm rule
  • Modifying alarm policies in an alarm rule
  • Disabling an alarm policy for one service in one-click monitoring
  • Resetting one-click monitoring
  • Modifying alarm policies in an alarm template
  • Deleting an alarm template and its associated alarm rules
  • Deleting a resource group associated with an alarm template
  • Removing resources from a resource group associated with an alarm template
  • Modifying or canceling an alarm template associated with a resource group
• Resolved (forcible clear): You can forcibly clear an alarm record or change the alarm rule to change the alarm status from Alarm, Alarm (triggered), or Insufficient data to Resolved (forcible clear). The operations are as follows:
  • Manually clearing an alarm record
  • Disabling an alarm rule
  • Disabling one-click monitoring