When Will an Alarm Rule Trigger an Insufficient Data Alarm?
Prerequisites
- You have created an alarm rule with No-Data Processing set to Generate no-data alarms in Advanced Settings.
- An alarm triggered by the alarm rule already exists in the alarm records and is not in the Expired state.
Triggering Mechanism
- Triggering condition
If a metric configured in the alarm rule does not report data for three consecutive hours, the system determines whether to generate an alarm indicating insufficient data.
- Resource and metric matching verification
The system checks whether the resource and metric whose monitoring data is not reported match the existing alarm records (with the same abnormal resource and alarm policy metric). The following status transition logic is executed only when they are matched.
- Status transition logic The system performs the following operations based on the current status of the matched existing alarm record:
- If the status is Resolved or Resolved (forcible clear), the system considers the fault as a new one and adds an Insufficient data alarm.
- If the status is Alarm, the system considers that the fault persists and updates the status of the existing alarm record to Insufficient data.
- If the status is Insufficient data, the system considers that the status remains unchanged and does not perform any operation. This prevents the same alarm from being generated repeatedly and reduces interference caused by invalid alarms.
Generally, if a cloud service metric does not report data for three consecutive hours, the data is considered insufficient. If the reporting period of a metric is longer than three hours and no monitoring data is reported for three consecutive periods, the data is also considered insufficient.
What is your overall rating for this page?
Thank 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