Use CloudMonitor to implement alert notifications for resource transfer-in events of the default resource group - Resource Management

After you enable the notification feature for resource transfer to the default resource group, CloudMonitor generates a system event if a resource is transferred to the default resource group. You can create an event subscription policy in CloudMonitor to notify you of such events through emails in a timely manner.

Background information

If you do not specify a resource group when you create a resource, the resource belongs to the default resource group by default. You need to transfer the resource from the default resource group to an appropriate resource group. This helps you accurately perform fine-grained access control, cost allocation, and automated O&M for resources by resource group.

We recommend that you specify a resource group when you create a resource or use the Automatic Resource Transfer feature to automatically assign resources to appropriate resource groups. In addition, you can use the feature described in this topic to quickly identify resources transferred to the default resource group, and then manually assign them to the appropriate resource groups.

Step 1: Enable the notification feature for resource transfer to the default resource group

Log on to the Resource Management console.
In the left-side navigation pane, choose Resource Group > Settings.
In the Notification of Resource Transfer to Default Resource Group section, click Enable.

If you do not require this feature, you can disable it at any time.

Step 2: View events of resource transfer to the default resource group

Log on to the Cloud Monitor console.
In the left-side navigation pane, choose Event Center > System Event.
On the Event Monitoring tab, configure filter conditions, as shown in the following figure, to view events of resource transfer to the default resource group.
Click Details in the Actions column of the desired event to view the event details in the JSON format.
Description of the Content field:
- ResourceType: the type of resource transferred to the default resource group.
- ResourceCount: the number of transferred resources of this type.
- StartTime: the start time of the statistical period for the event.
- EndTime: the end time of the statistical period for the event.
Important
- Resource Group aggregates transfer events and push events of resource transfer to the default resource group to CloudMonitor every minute. StartTime specifies the start time of the one-minute period, and EndTime specifies the end time of the one-minute period.
- If multiple types of resources are transferred to the default resource group within a one-minute period (StartTime to EndTime), multiple events are generated. One event is for only one resource type.
Example of the Content field:
You transfer two Elastic Compute Service (ECS) instances and three Object Storage Service (OSS) buckets to the default resource group at 10:00:02 and 10:00:40 on March 21, 2025, respectively. In this case, Resource Group pushes two events of resource transfer to the default resource group at 10:01:00 on March 21, 2025. The Content field in the two events are as follows:
```
{
	"Content": {
		"ResourceType": "ecs.instance",
		"ResourceCount": 2,
		"StartTime": "2025-03-21 10:00:00",
		"EndTime": "2025-03-21 10:01:00"
	}
}
```
```
{
	"Content": {
		"ResourceType": "oos.bucket",
		"ResourceCount": 3,
		"StartTime": "2025-03-21 10:00:00",
		"EndTime": "2025-03-21 10:01:00"
	}
}
```

Step 3: Configure event alert notifications

Create an alert contact.
1. Log on to the Cloud Monitor console.
2. In the left-side navigation pane, choose Alerts > Alert Contacts.
3. On the Alert Contacts tab, click Create Alert Contact.
4. In the Set Alert Contact panel, enter a name and an email address for the alert contact.
  Note
  For information about how to configure a DingTalk, Lark, WeCom, or Slack Webhook URL, see Create an alert contact.
5. After you confirm that the information is correct, click OK.
6. Activate the email address of the alert contact.
  By default, the email address of the alert contact is in the Pending Activation state. After the alert contact receives an email that contains the activation link, the alert contact must activate the email address within 24 hours. Otherwise, the alert contact cannot receive alert notifications. After the email address is activated, you can view the email address in the alert contact list.
Create an alert contact group.
1. On the Alert Contacts page, click the Alert Contact Group tab.
2. On the Alert Contact Group tab, click Create Alert Contact Group.
3. In the Create Alert Contact Group panel, enter a name for the alert contact group and add alert contacts to the alert contact group.
4. Click Confirm.

Create a notification configuration policy.

In the left-side navigation pane, choose Event Center > Notification Configuration.
On the Notification Configuration page, click Create policy.

In the Create Policy panel, configure the parameters for the notification configuration policy.

Parameter	Description
Name	The name of the notification configuration policy.
Description	The description of the notification configuration policy.
Notification	The first notification object of the alert. Valid values for Notification Settings: Set Notification Group Directly: Select an alert contact group. In this example, select the alert contact group created in Step 2. Set the notification group by severity: Select an alert contact group based on the following levels: Critical, Warning, Notification (Info), and Resolved.

Create a subscription policy.
1. In the left-side navigation pane, choose Event Center > Event Subscription.
2. On the Subscription Policy tab, click Create Subscription Policy.
3. On the Create Subscription Policy page, configure the parameters.
  - Basic information: Enter a name and a description for the subscription policy.
  - Alert Subscription: Specify a subscription type and a subscription scope.
    Subscription type: Select System Events.
    Subscription scope:
    Products: Select Resource Management.
    Event Type: Select DefaultResourceGroup.
    Event name: Select ResourceGroup:DefaultResourceGroup:AddResources.
    Event Level: Optional. Configure this parameter based on your business requirements. The default setting is used in this example.
    Application grouping: Optional. Configure this parameter based on your business requirements. The default setting is used in this example.
    Event Content: Optional. Configure this parameter based on your business requirements. If you do not want to receive notifications when some types of resources are transferred to the default resource group, select Set as blacklist and enter the resource types in the <cloud service code.resource type> format. For more information, see Services that work with Resource Group. As shown in the preceding figure, notifications are not sent when ECS disks, ECS images, and ECS snapshots are transferred to the default resource group.
    Event Resources: Optional. Configure this parameter based on your business requirements. The default setting is used in this example.
  - Combined Noise Reduction: Optional. Configure this parameter based on your business requirements.
    For example, if you select Event name for Merge Content and Direct trigger, suppress notification after trigger 5Minutes for Noise Reduction, a regular notification is sent when resources are transferred to the default resource group, and the remaining notifications are suppressed.
  - Notification: Select the notification configuration policy created in Step 3 and specify notification methods such as emails. In this example, emails are selected for notifications.
  - Push and Integration: Optional. Configure this parameter based on your business requirements. In this example, this parameter is not configured.
4. Click Submit.

Step 4: View alert notifications

When resources are transferred to the default resource group, you can receive notifications based on the configured notification methods. The following figure shows a notification that is sent through an email.