Creating an Alarm Rule to Monitor an Event
Scenarios
This topic describes how to create an alarm rule to monitor an event.
Procedure
- Log in to the management console.
- Click Service List in the upper left corner and select Cloud Eye.
- In the navigation pane on the left, choose Event Monitoring.
- On the event list page, click Create Alarm Rule in the upper right corner.
You can also click Create Alarm Rule in the Operation column of the target event. When you create an alarm rule, related event parameters are preset.
- On the Create Alarm Rule page, configure the parameters.
- Set the alarm rule name and description.
Table 1 Parameters for configuring alarm rules Parameter
Description
Name
Specifies the alarm rule name. The system generates a random name, which you can modify.
Description
(Optional) Provides supplementary information about the alarm rule.
- Select a monitored object and configure alarm content parameters.
Table 2 Parameters for configuring alarm content Parameter
Description
Resource Type
Specifies the type of the resource the alarm rule is created for.
Event Type
Specifies the event type, which can be System event or Custom event.
Event Source
Specifies the service the event is generated for.
Example value: Elastic Cloud Server
For a custom event, set Event Source to the value of event_source.
Monitoring Scope
Specifies the monitoring scope for event monitoring.
Example value: All resources
Method
Specifies the means you use to create the alarm rule.
Event Name
Specifies the event name.
For events supported by event monitoring, see Events Supported by Event Monitoring.
Example value: Delete ECS
Monitored Object
Specifies the object to be monitored. This parameter is mandatory if you set Monitoring Scope to Specific resources.
Trigger Mode
You can select immediate trigger or accumulative trigger based on the operation severity.
Example value: Immediate trigger
Alarm Policy
Specifies the policy for triggering an alarm.
For example, an alarm is triggered if the event occurred for three consecutive periods of 5 minutes.
NOTE:This parameter is mandatory when Triggering Mode is set to Accumulative Trigger.
Alarm Severity
Specifies the alarm severity, which can be Critical, Major, Minor, or Informational.
Example value: Major
Operation
Select Delete to delete the alarm policy.
- Configure the alarm notification.
Figure 1 Alarm notification
Table 3 Parameters for configuring alarm notifications Parameter
Description
Alarm Notification
Specifies whether to notify users when alarms are triggered. Notifications can be sent by email, SMS message, or HTTP/HTTPS message.
Notification Object
Specifies the object to which alarm notifications will be sent. You can select the account contact or a topic.
- The account contact is the tenant owner. If a user registers both a mobile number and an email address, they will receive alarm information through both channels. However, if only one of these contact methods is registered, the alarm information will be sent exclusively to that registered one.
- A topic is a specific event type for publishing messages or subscribing to notifications. If the required topic is not available, create one first and add subscriptions to it. For details, Creating a Topic and Adding Subscriptions.
Validity Period
Cloud Eye sends notifications only within the validity period specified in the alarm rule.
If Validity Period is set to 08:00-20:00, Cloud Eye sends notifications only from 08:00 to 20:00.
Trigger Condition
Specifies the condition for triggering an alarm notification.
- Select an enterprise project.
Figure 2 Advanced Settings
Table 4 Name and Description Parameter
Description
Enterprise Project
Specifies the enterprise project that the alarm rule belongs to. Only users with the enterprise project permissions can view and manage the alarm rule. For details about how to create an enterprise project, see Creating an Enterprise Project.
- Click Create.
- Set the alarm rule name and description.
Feedback
Was this page helpful?
Provide feedbackThank 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