Creating an Alarm Rule
Cloud Eye allows you to use alarm templates to create alarm rules, making it easy and convenient to add or modify alarm rules for resources or cloud services, especially for a large number of resources and cloud services.
You can use a default alarm template to create an alarm rule for a cloud service resource.
You can create alarm rules for CBR.
Creating an Alarm Rule Using Cloud Eye
- Log in to the Cloud Eye console.
- Under Management & Deployment, select Cloud Eye. In the navigation pane, choose Alarm Management > Alarm Rules.
- On the displayed page, click Create Alarm Rule in the upper right corner.
- On the displayed Create alarm rule page, configure the parameters.
- Set Name and Description.
Parameters for configuring the rule name and description
Parameter
Description
Example Value
Name
Name of the alarm rule. Cloud Eye will generate a random name, but you can modify it.
alarm-cgnw
Description
Alarm rule description. This parameter is optional.
-
- Configure alarm content parameters.
- If you select Cloud Backup and Recovery for Resource Type, vaults are monitored with two metrics. Table 1 describes the parameters.
Table 1 Parameters Parameter
Description
Example Value
Resource Type
Cloud Backup and Recovery is selected in this example.
Cloud Backup and Recovery
Dimension
Monitoring dimension. By default, monitoring is performed by vault.
Vault
Monitoring Scope
Choose the vaults you want to monitor from the list.
vault-56f8
Method
You can create an alarm rule by using the template or manually creating it.
NOTE:If you set Monitoring Scope to Specific resources, you can set Method to Use template.
Use template
Template
Template to be used.
-
Alarm Policy
Policy for triggering an alarm.
If you set Resource Type to a specific cloud service, the alarm policy takes effect periodically. If you set Resource Type to Event Monitoring, the alarm policy takes effect based on specific events.
Currently, the following CBR monitoring metrics are supported:
- Vault Usage
- Used Vault Size
-
Alarm Severity
Alarm severity, which can be Critical, Major, Minor, or Informational.
Major
- If you set Resource Type to Event Monitoring, CBR resources are monitored based on specific events. Table 2 describes the parameters.
Table 2 Parameters Parameter
Description
Example Value
Resource Type
Event Monitoring is selected in this example.
Event Monitoring
Dimension
Metric dimension of the selected resource type.
System event
Monitoring Scope
Monitoring scope for event monitoring.
Default value: All resources
-
Method
Select Configure manually.
Configure manually
Alarm Policy
Policy for triggering an alarm.
Table 3 lists the supported CBR events that trigger alarms.
-
Table 3 CBR events that trigger alarms Event Name
Severity
Description
Solution
Impact
Backup creation failed
Critical
The backup creation failed.
Manually create a backup or contact the administrator.
Data may be lost.
Resource restoration from a backup failed
Critical
The resource restoration from a backup failed.
Restore the resource using another backup or contact the administrator.
Data may be lost.
Backup deletion failed
Critical
The backup deletion failed.
Try again later or contact the administrator.
Billing may be abnormal.
Vault deletion failed
Critical
The vault deletion failed.
Try again later or contact the administrator.
Billing may be abnormal.
Replication failure
Critical
The backup replication failed.
Try again later or contact the administrator.
Data may be lost.
Backup task created
Major
The backup task was created.
None
None
Resource restored from a backup
Major
The resource was successfully restored from a backup.
Check that data is successfully restored.
None
Backup deleted
Major
The backup was deleted successfully.
None
None
Vault deleted
Major
The vault was deleted successfully.
None
None
Replication success
Major
The backup was replicated successfully.
None
None
You can change the alarm severity as needed.
- If you select Cloud Backup and Recovery for Resource Type, vaults are monitored with two metrics. Table 1 describes the parameters.
- Configure alarm notifications.
Table 4 Parameters for configuring alarm notifications Parameter
Description
Example Value
Alarm Notification
Whether to notify users when alarms are triggered. Notifications can be sent by email or text message, or through HTTP/HTTPS request to servers.
You can enable (recommended) or disable Alarm Notification.
-
Notification Window
Cloud Eye sends notifications only within the notification window specified in the alarm rule.
If Notification Window is set to 00:00-8:00, Cloud Eye sends alarm notifications only within 00:00-8:00.
-
Notification Object
The name of the topic the alarm notification is to be sent to.
If you enable alarm notification, you need to select a topic. If no desirable topics are available, create one and subscribe to it first. For details about how to create a topic, see the Simple Message Notification User Guide.
-
Trigger Condition
The condition for triggering the alarm notification. You can select Generated alarm, Cleared alarm, or both.
-
- Click Create.
- Set Name and Description.
After the alarm rule is created, if the metric data reaches the specified threshold or there is a CBR event, Cloud Eye immediately informs you that an exception has occurred. For details, see the Cloud Eye User Guide.
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