Creating Alarm Rules

Scenarios

You can create alarm rules to monitor the usage of OBS resources or key operations on OBS resources. After an alarm rule is created, Cloud Eye immediately notifies you of any exceptions with your OBS resources in real time if the monitoring metric reaches the specified threshold or a specified event occurs.

Billing

If you use SMN to send alarm notifications, you will be billed for the message notifications and downstream Internet traffic. For details, see Billing.

Permissions Control

To set alarm rules, your account must have the CES FullAccess permission. If you are prompted that you do not have the required permissions, contact the administrator for authorization. For details, see Assigning Permissions to an IAM User.

Setting Alarm Rules

1. Go to the Create Alarm Rule page of the Cloud Eye console.
2. Configure the alarm name as prompted.
   Figure 1 Configuring the alarm name
   

   Table 1 Basic information parameters of an alarm rule

   Parameter	Example Value	Description
   Name	alarm-obs	Name of the alarm rule. The system generates a name randomly, and you can change it as you want. The name can contain a maximum of 128 characters. Only letters, digits, underscores (_), and hyphens (-) are allowed.

3. Select an alarm type.
   • If you select Metric for Alarm Type, you can create an alarm rule for OBS metrics. Then go to 4.
   • If you select Event for Alarm Type, you can create an alarm rule for OBS events. Then go to 5.

4. Configure alarm policies.

   Configure the key parameters as described below. Keep the default settings for other parameters. For details about how to set alarm rule parameters, see Creating an Alarm Rule.

   

   

   Table 2 Key parameters for creating an alarm rule (metric monitoring)

   Parameter	Example Value	Description
   Alarm Type	Metric	Select the alarm type for which you want to set an alarm rule. The following types are supported: Metric: Set an alarm threshold for a metric to trigger an alarm. Event: Set an alarm rule for event monitoring. When a specified event occurs, an alarm is triggered.
   Cloud Product	Object Storage Service - Bucket Name	Select the cloud service for which the alarm is reported. OBS supports the following two dimensions: Object Storage Service - Bucket Name: If you select the bucket name dimension, the alarm rule takes effect for metrics of a single bucket. Object Storage Service-User: If you select the user dimension, the alarm rule takes effect for aggregated metrics of all buckets of the user.
   Resource Level	Cloud product (Recommended)	Resource level of the monitored object. You can select Cloud product or Specific dimension. Cloud product (Recommended): Alarm rules can be configured across dimensions. Specific dimension: Alarm rules cannot be configured across dimensions.
   Monitoring Scope	Specific resources	Scope of resources for which the alarm rule takes effect in the specified dimension. The following options are supported: All resources: An alarm will be triggered when the metric of any resource (including newly created ones) in the specified dimension meets the alarm policy. Resource groups: An alarm is triggered when the metric of resources in the selected group in the specified dimension meets the alarm policy. Specific resources: An alarm is triggered when the metric of the specific resources in the specified dimension meets the alarm policy.
   Use Template (Optional)	-	Custom alarm template used to set the alarm triggering rule. This parameter is mandatory when an alarm policy template is required. For details about how to create a custom alarm template, see Creating a Custom Metric or Event Template.
   Alarm Policy	If the number of GET requests for a specified bucket reaches the following threshold for three consecutive times: ≥ 10,000, a warning alarm is triggered. ≥ 50,000, a minor alarm is triggered. ≥ 100,000, a major alarm is triggered. ≥ 150,000, a critical alarm is triggered. In addition, after an alarm is triggered, the alarm is reported every hour. NOTE: The preceding descriptions are only examples. Configure the policy based on your service requirements.	Select the monitoring metric you want to set for the alarm policy. For details about the monitoring metrics, see OBS Monitoring Metrics. This parameter is mandatory when no alarm policy template is used.

5. Configure an event alarm policy.

   Configure the key parameters as described below. Keep the default settings for other parameters. For details about how to set alarm rule parameters, see Creating an Alarm Rule.

   

   

   Table 3 Key parameters for creating an alarm rule (event monitoring)

   Parameter	Example Value	Description
   Alarm Type	Event	Select the alarm type for which you want to set an alarm rule. The following types are supported: Metric: Set an alarm threshold for a metric to trigger an alarm. Event: Set an alarm rule for event monitoring. When a specified event occurs, an alarm is triggered.
   Event Type	System event	This parameter is required if Alarm Type is set to Event. You can select System event or Custom event. System event: The alarm rule takes effect for system-defined events. Custom event: The alarm rule takes effect for events generated by a specified event source.
   Event Source	Object Storage Service	Source of the event for which the alarm rule takes effect. If Event Type is set to System event and Event Source is set to a specified cloud service, the alarm rule takes effect for the events defined by the cloud service system. If Event Type is set to Custom event and Event Source is set to a specified resource, the alarm rule takes effect for events from the specified source. For details about the event source configuration requirements, see the event_source parameter.
   Monitoring Scope	Specific resources	Scope of resources for which the alarm rule takes effect. The following types are supported: All resources: An alarm will be triggered when the event of any resource (including newly created ones) meets the alarm policy. Specific resources: An alarm will be triggered when the event of a specific resource meets the alarm policy.
   Use Template (Optional)	-	Custom event alarm template used to set the event alarm triggering rule. This parameter is mandatory when an alarm policy template is required. For details about how to create a custom alarm template, see Creating a Custom Metric or Event Template.
   Alarm Policy	If the Create bucket event is triggered 10 times Within 5 minutes, a Major alarm is generated Every 5 minutes. If the Delete bucket event is triggered 1 times Within 5 minutes, a Major alarm is generated Every 5 minutes. If the Set bucket policy event is triggered 1 times Within 5 minutes, a Minor alarm is generated Hourly. NOTE: The preceding descriptions are only examples. Configure the policy based on your service requirements.	Select the event you want to set to configure the alarm policy. For details about event monitoring, see Monitored OBS Events. This parameter is mandatory when no alarm policy template is used.

6. Click Create.

   If the new alarm rule is displayed in the alarm rule list, the rule is created successfully.

Managing Alarm Rules

You can perform the operations listed below on alarm rules.

Alarm Notifications

Once alarm notifications are configured, the system notifies you in real time through SMS messages, emails, or voice calls whenever a cloud service metric breaches an alarm threshold. This allows you to stay informed of the status changes of your cloud resources. For details about how to create a notification policy, see Creating a Notification Policy.

You can configure alarm notifications when creating an alarm rule. For details, see Creating an Alarm Rule. You can also modify alarm notifications after an alarm rule is created. For details, see Modifying the Notification Settings of an Alarm Rule.