Creating an Alarm Rule to Monitor an Event

Billing

Alarm notifications sent by SMN will be billed based on their frequency and message length. For details, see Product Pricing Details.

Creating an Alarm Rule and Notification for Event Monitoring

1. Log in to the Cloud Eye console.

2. In the navigation pane, choose Event Monitoring.
3. Click Create Alarm Rule in the upper right corner to go to the Create Alarm Rule page.
   

   If you want to create an alarm rule for a specific event, locate the event in the event list and click Create Alarm Rule in the Operation column. On the displayed Create Alarm Rule page, required parameters have been configured for that event.

4. Configure basic information about the alarm rule.

   Table 1 Basic parameters

   Parameter	Description	Example Value
   Name	Name of the alarm rule. The system generates a random name, which you can modify. The rule name cannot exceed 128 characters and can contain only letters, digits, underscores (_), and hyphens (-).	alarm-c3dv
   Alarm Type	Type of alarms that the alarm rule applies to. The default value is Event.	Event
   Event Type	This parameter is only available if Alarm Type is set to Event. You can select either System event or Custom event. For details about the events supported by each cloud service, see Events Supported by Event Monitoring.	System event
   Event Source	This parameter is only available if Alarm Type is set to Event. If Event Type is set to System event, select the cloud service from which the event comes. If Event Type is set to Custom event, the event source must be the same as that of the reported source. For details about how to report an event, see Reporting Events.	Elastic Cloud Server
   Monitoring Scope	Monitoring scope the alarm rule applies to. All resources: An alarm will be triggered if any resource in the selected cloud product meets the alarm policy. Resource groups: An alarm will be triggered if any resource in the selected resource group meets the alarm policy. Specific resources: Click Select Specific Resources to select resources. An alarm will be triggered if any selected resource meets the alarm policy. NOTE: This parameter is available when Event Type is set to System event. Currently, Resource groups can be selected as the monitoring scope only when the event source is ECS (supported only in certain regions; for details, check the console), DDS, RDS, DCS, or GeminiDB.	Specific resources
   Group	When Monitoring Scope is set to Resource groups, you need to select a group. If no resource group meets your needs, click Create Resource Group to create one. After selecting a resource group from the drop-down list, you can click View Resource Details in a Group to view the details of resources in the group. After an alarm rule is configured, the group cannot be modified.	-
   Dimension	When you set Monitoring Scope to Specific resources, select a dimension of the resources to connect the event data of the selected cloud service to Cloud Eye by dimension.	Document Database Instances

5. Configure alarm policy parameters as prompted. For details about alarm policy parameters, see Alarm Policy Parameters.
6. Configure alarm notification parameters as prompted.
   Figure 1 Configuring the alarm notification
   

   Table 2 Parameter description

   Parameter	Description
   Alarm Notifications	Whether to send alarm notifications by SMS, email, FunctionGraph (function), FunctionGraph (Workflow), WeCom, DingTalk, Lark, WeLink, HTTP, or HTTPS. This parameter is enabled by default.
   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. 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.
   Notification Window	Notification window during which Cloud Eye only sends notifications. If you set this parameter to 08:00 to 20:00, Cloud Eye only sends notifications within this period.
   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.
   Trigger Condition	If you set Alarm Type to Event, you can select Generated alarm for this parameter.
   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.

7. Configure parameters in Advanced Settings.
   Figure 2 Advanced settings
   

   Table 3 Parameter description

   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.
   Tag	Each tag is a key-value pair. You can tag cloud resources to easily categorize and search for them. You can create tags using 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.

8. Click Create.

   You can go to the Alarm Rules page and check the alarm rule you created. You can filter the new alarm rule by its name.