Help Center/ Cloud Eye/ Troubleshooting/ Alarm Management/ How Do I Handle an Insufficient Data Alarm Generated After a Resource Is Deleted?
Updated on 2026-10-28 GMT+08:00

How Do I Handle an Insufficient Data Alarm Generated After a Resource Is Deleted?

Symptom

After you delete a cloud service resource, the status of an alarm generated for the resource remains Insufficient data in the alarm records.

Possible Causes

An Insufficient data alarm is triggered when the monitoring data is interrupted for a period longer than the specified one. This alarm is used to notify you of data collection exceptions.

After you delete a cloud service resource, the alarm rules configured for the resource in Cloud Eye remain effective. Because the resource has been deleted, no monitoring data is reported. Generally, an Insufficient data alarm is generated when no monitoring data is reported for the metric configured in an alarm rule for three consecutive hours. For details, see When Will an Alarm Rule Trigger an Insufficient Data Alarm?

Data reporting cannot be restored for deleted resources, and the system lacks a signal for data restoration. Therefore, the alarm cannot be automatically cleared.

Impact

If an alarm remains in the Insufficient data state for a long time, it keeps drawing O&M attention and may be mistakenly considered a real fault, interfering with routine O&M.

Solution

  1. Log in to the Cloud Eye console.
  1. In the navigation pane, choose Alarm Management > Alarm Handling. The Alarm Records page is displayed.

    In some regions, the path is Alarm Management > Alarm Records.

  2. In the alarm list, locate the target alarm whose status is Insufficient data.

    You can check whether the alarm is generated for a deleted resource based on the Resource Type and Abnormal Resource information in the alarm list.

    Figure 1 Insufficient data alarm
  3. Click Forcibly Clear Alarm in the Operation column of the alarm record. The Forcibly Clear the Alarm dialog box is displayed.
    Figure 2 Forcibly clearing an alarm
  4. Click OK.

    In the alarm record list, the status of the alarm record will be updated to Resolved (forcible clear). Subsequent O&M will not be affected.

Preventive Measures

  1. Before deleting a resource, if you do not need to pay attention to its alarms, you can delete or disable the alarm rules associated with the resource. For details about how to delete an alarm rule, see Deleting Alarm Rules. For details about how to disable an alarm rule, see Disabling Alarm Rules.
  2. After releasing resources in batches, check whether there are associated alarm rules and clear them in a timely manner.