Creating a Resource Group
If you use multiple types of cloud services, you can add all related resources, such as ECSs, BMSs, EVS disks, EIPs, bandwidths, and databases to the same resource group for easier management and O&M.
| Add Resources | Match Resources By | Description |
|---|---|---|
| Automatically | Instance name | Set a rule to match resources by instance name. All matched instances are automatically added to the resource group for management. |
| Enterprise project | If you have added resources to enterprise projects, you can create a resource group and match resources by enterprise project. Then, all instances in the specified enterprise projects are added to the resource group for management. To change enterprise projects specified for a resource group, see Removing Resources from an Enterprise Project and Adding Resources to an Enterprise Project. | |
| Tag | If your instances have been tagged, you can create a resource group and match resources by tag. Then, all matched instances are added to the resource group for management. For details about how to create and add tags, see Adding Resource Tags. | |
| Multiple criteria | Add resources using multiple matching rules. If you set Resource Level to Specific dimension, you can only select both Enterprise project and Tag for Multi-Criteria Match. | |
| Manually | -- | To manage existing fixed instances based on your service needs, manually select resources for the resource group. |
Billing
Alarm notifications sent by SMN will be billed based on their frequency and message length. For details, see Product Pricing Details.
Prerequisites
If you have manually added resources to your resource group and set Resource Level to Specific dimension, make sure the metric or event dimension matches the resource group's dimension when creating alarm rules. Check the specific cloud service documentation for details on metric or event dimensions. You can click reference links for metrics in Cloud Product Metrics and events in Events Supported by Event Monitoring.
Constraints
- You can create up to 1,000 resource groups.
- Each resource group can contain 1 to 10,000 cloud service resources.
- There are limits on the number of different types of resources in a resource group. For details, check the tips on the Cloud Eye console.
- After a resource group is created, it takes about 3 hours for the new resource group rule to be applied.
Creating a Resource Group
The new resource group creation page is now available in some regions. It allows you to link alarm notifications during resource group creation. This feature will expand to other regions soon. For details, check the console.
- Log in to the Cloud Eye console.
- In the navigation pane, choose Resource Groups.
- In the upper right corner, click Create Resource Group.
- On the Create Resource Group page, enter a group name. Select the way you want to add a resource and define resource matching rule as required. Supported cloud services vary with how resources are added. For details, see Cloud Services Supported by Resource Groups.
(Optional, Earlier Edition) Advanced Settings
You can configure whether to associate an alarm template and send alarm notifications when creating a resource group or afterward. This configuration streamlines alarm rules management and simplifies alarm rule configuration. For details, see Associating a Resource Group with an Alarm Template.
- In the Advanced Settings area, select the template to be associated.
- Configure alarm notifications.
Table 7 Configuring alarm notifications Parameter
Description
Enterprise Project
Enterprise project that the alarm rules belong 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.
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 Policies
If Notified By is set to Notification policies, you need to select one or more notification policies. You can specify the notification group, window, template, and other parameters in a notification policy. For details, see Creating, Modifying, or Deleting a Notification Policy.
Notification Group
If Notified By is set to Notification groups, you need to select the notification groups to which alarm notifications will be sent. Select or create a notification template and set the notification window. For details about how to create a notification group, see Creating a Recipient and Notification Group.
Recipient
Target recipient of alarm notifications. You can select the account contact or a topic. This parameter is available only if Notified By is set to Topic subscriptions. If there is a display name of a topic, the format is Topic name (Display name), and you can search for a topic by name or display name. If no display name is set for a topic, only the topic name will be displayed.
- The account contact is the mobile number and email address of the registered account.
- A topic is used to publish messages and subscribe to notifications. If there is no topic you need, create one first and add subscriptions to it. For details, see Creating a Topic and Adding Subscriptions.
Notification Templates
This parameter is available only when you select Contact groups or Topic subscriptions for Notified By. You can select an existing template or create a new one.
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.
Notification Window
Cloud Eye sends notifications only within the validity period specified in the alarm rule.
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
Condition that will trigger an alarm notification. You can select Generated alarm (when an alarm is generated), Cleared alarm (when an alarm is cleared), or both.
(New Edition) Alarm Notification Parameters
When creating a resource group, you can configure whether to send alarm notifications. When associating a custom metric alarm template with a resource group, you can choose whether the alarm rules in the template inherit the alarm notification settings of the resource group.
| Parameter | Description | Example Value |
|---|---|---|
| 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. | Enabled |
| Notified By | Notification method. Select Notification policies, Contact groups, or Topic 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.
| 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. | - |
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