lboka/doc-exports
1
0
Fork 0
forked from docs/doc-exports
Code Pull Requests Activity
doc-exports/docs/ces/umn/ces_01_0076.html
gtema f6f2ca6fa5 Update CES UMN 
Reviewed-by: Hasko, Vladimir <vladimir.hasko@t-systems.com>
Co-authored-by: gtema <artem.goncharov@gmail.com>
Co-committed-by: gtema <artem.goncharov@gmail.com>
2022-12-07 15:46:48 +00:00

3.2 KiB
Raw Permalink Blame History

Viewing Alarm History

The Alarm History page can display the status changes of all alarm rules in the last 30 days.

When an alarm is generated, you can view the alarm details about the cloud resource.

Procedure

  1. Log in to the management console.
  2. In the upper left corner, select a region and project.
  3. Click Service List in the upper left corner, and select Cloud Eye.
  4. Choose Alarm Management > Alarm History.

    On the Alarm History page, you can view the status changes of all alarm rules from the last 7 days.

    • You can select a time range to view the alarm history.
    • In the upper right corner of the alarm record list, you can filter the Alarm History by the alarm rule name, resource ID, and alarm rule ID.
  5. Click the target alarm rule to go to its details page. In the lower part of the displayed page, you can view the alarm history of the selected alarm rule from the last 30 days.
    In the Alarm History list, you can check whether resources are abnormal and handle the exceptions, if any.
    • Typically, alarms are triggered based on calculation. Therefore, the alarm triggering time may be a few seconds later than the time the threshold was reached.
    • If you have created or modified an alarm rule after obtaining the monitoring data and an alarm is triggered, the alarm triggering time is the time when you created or modified the alarm rule.
Parent topic: Using the Alarm Function