Creating an Alarm Rule for a Cloud Service
To monitor the metric data of an instance, you can create an alarm rule for a specified resource and configure alarm notifications on the Cloud Service Monitoring page. If the value of a resource metric reaches the specified threshold, Cloud Eye will immediately notify you of the resource exception through SMN, preventing service loss. For details about how to create alarm rules for multiple instances of a cloud service, see Creating an Alarm Rule.
Creating an Alarm Rule for a Specific Instance
- Log in to the Cloud Eye console.
- In the navigation pane, choose Cloud Service Monitoring.
- Click the name of the cloud service dashboard you want to view.
- In the instance list, locate the row that contains the target instance and choose More > Create Alarm Rule in the Operation column.
- On the displayed page, the monitored object is the selected resource by default. Configure the alarm policy, alarm notification, and advanced settings as required.
For details about alarm policy parameters, see Alarm Policy Parameters.
Table 1 Configuring alarm notifications Parameter
Description
Example Value
Alarm Notifications
Whether to send alarm notifications by SMS, email, FunctionGraph (function), FunctionGraph (Workflow), WeCom, DingTalk, Lark, WeLink Chatbot, HTTP, or HTTPS. This parameter is enabled by default.
Enabled
Notified By
Notification method. You can select Notification policies, Contact groups, or Topic subscriptions.- Notification policies: If several O&M owners handle service maintenance, you can set up different notification scopes in a notification policy to alert specific owners by Alarm Severity or at a specified schedule. By configuring multiple notification scopes in a notification policy, you can implement alarm severity-based notification and personnel scheduling. For details, see Creating a Notification Policy.
- Contact groups: Cloud Eye provides alarm notification capabilities. Select this option if you do not need to send alarm notifications by severity or schedule. To send alarm notifications to a group of contacts, you can create a contact group and add contacts to it in Cloud Eye for easier management. For details, see Creating a Contact/Contact Group.
- Topic subscriptions: If the current region does not support alarm notifications or the recipients have been configured in SMN, you can select a topic created in SMN or your cloud account contact as required.
For details, see Creating a Topic and Adding Subscriptions.
NOTE:Cloud Eye uses SMN for alarm notifications. If SMN has major delays, the alarm notifications may also be delayed.
Contact groups
Notification Window
If Notified By is set to Contact groups or Topic subscriptions, you need to set the notification window.
Cloud Eye sends notifications only within the validity period specified in the alarm rule.
For example, if the notification window is set to 08:00 to 20:00, notifications are sent only within this specified time range when a metric reaches the specified threshold or a specified event occurs.
08:00-20:00
Time Zone
Time zone for the alarm notification window. By default, it matches the time zone of the client browser, but can be manually configured.
(GMT+08:00) Beijing, Chongqing, Hong Kong, Urumqi, Kuala Lumpur, Singapore, Perth, Taipei, Irkutsk, Ulaanbaatar
Trigger Condition
This parameter is required when you set Notified By to Contact groups or Topic subscriptions.
- If you set Alarm Type to Metric, select Generated alarm, Cleared alarm, or both for this parameter.
- If you set Alarm Type to Event, you can only select Generated alarm for this parameter.
Generated alarm
Notification Template
This parameter is only available if you set Notified By to Contact groups or Topic subscriptions. You can select an existing template or create one to send alarm notifications.
NOTE:Some cloud services do not support fields such as the resource name, enterprise project, resource tag, private IP address, and public IP address in the notification template. When you select a system template as the notification template, these fields will appear blank in the alarm notifications even if you have them configured.
-
Table 2 Advanced settings Parameter
Description
Enterprise Project
Enterprise project that the alarm rule belongs to. Only users with the enterprise project permissions can manage the alarm rule. For details about how to create an enterprise project, see Creating an Enterprise Project.
Tags
Key-value pairs that you can use to easily categorize and search for cloud resources. You are advised to create predefined tags in TMS. For details, see Creating Predefined Tags.
If you have configured tag policies for Cloud Eye, add tags to alarm rules based on the tag policies. If you add a tag that does not comply with the tag policies, alarm rules may fail to be created. Contact your administrator to learn more about tag policies.
- A key can contain up to 128 characters, and a value can contain up to 255 characters.
- You can create up to 20 tags.
Description
(Optional) Alarm rule description. It can contain up to 256 characters.
No-Data Processing
If Alarm Type is set to Metric, you can configure how to handle no-data alarms. You can choose to send an alarm, consider the alarm cleared, or take no action.- Generate no-data alarms: If a metric configured in the alarm rule does not report data for three consecutive hours, an alarm record will be generated indicating insufficient data.
- Treated as cleared: If a metric configured in the alarm rule does not report data for three consecutive hours, the alarm record generated by the current alarm rule will be treated as cleared.
- No action: If a metric configured in the alarm rule does not report data for three consecutive hours, no alarm record indicating insufficient data will be generated, and the alarm record generated by the alarm rule will not be cleared.
NOTE:- 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.
- In some regions, a switch is provided to determine whether to generate an alarm when no data is reported. By default, this switch is enabled. When enabled, an insufficient data alarm record will be generated if the configured metric reports no data for three consecutive hours.
- Click Create.
The new alarm rule is displayed in the alarm rule list.
Viewing an Alarm Rule
- Log in to the Cloud Eye console.
- In the navigation pane, choose Cloud Service Monitoring.
- Click the name of the cloud service dashboard you want to view.
- In the instance list, locate the row that contains the target instance and choose More > View Alarm Rule in the Operation column.
- In the displayed dialog box, view all alarm rules and alarm policies of the instance. Click an alarm rule to go to its details page.
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