Help Center/ Cloud Eye/ Best Practices/ Cloud Eye Resource Group Configuration/ Resource Group Overview
Updated on 2025-12-23 GMT+08:00
View PDF
Share

Resource Group Overview

A typical e-commerce project includes several connected subsystems. Each handles specific functions and collaborates to deliver the full service experience. If the customer's e-commerce project uses systems from various suppliers, each system owner must handle alarms for their specific resources.

This practice describes how to use resource groups in Cloud Eye to send alarms to the correct O&M personnel, thereby avoiding alarm flooding and invalid notifications.

What Is a Resource Group?

Resource groups allow you to centrally manage services involved in your businesses. You can manage different types of resources, alarm rules, and alarm records by business, which quickly improves O&M efficiency.

Metric and Event Notification Solutions for Cloud Eye

Table 1 Metric and event notification solutions

Alarm Type

Configuration

Scenario

Remarks/Risk Point

Metric

Create a resource group and set Add Resources to Automatically and Match Resources By to Tag.

Tags have been added for resources and the tags are complete.

This solution depends on the accuracy of tags added for resources.

Create a resource group and set Add Resources to Automatically and Match Resources By to Enterprise project.

No tag is added for the resources of the account.

This solution only allows you to select enterprise projects. It is suitable for accounts with only one environment.

Create a resource group and set Add Resources to Automatically and Match Resources By to Multiple criteria.

Enterprise projects have been configured for resources, and no tag related to rights- and domain-based management has been added.

This solution allows you to match resources by enterprise project, tag, and instance name. It is suitable for accounts with a small number of tags. If a large number of tags are added for resources, the matching will be complex.

Create a resource group and set Add Resources to Automatically and Match Resources By to Instance name.

The account's resources have no tags and are not bound to any enterprise project.

The solution relies on resource naming rules, making it hard to execute. Therefore, it is not recommended.

Create a resource group and set Add Resources to Manually and Resource Level to Cloud product.

Cloud services that do not support automatic resource addition or resource match by tag.

For details about these services, see Cloud Services Supported by Resource Groups.

Create a resource group and set Add Resources to Manually and Resource Level to Specific dimension.

Other scenarios where you need to manually create a resource group. For example, some resources require specific thresholds.

If you only want to monitor metrics of a specific dimension, set Resource Level to Specific dimension.

Event

Create an alarm rule of the event type. Set the monitoring scope to specified resources.

Event alarms require rights- and domain-based management.

When you select specified resources, you can filter resources by resource group.

Each alarm rule applies to only one cloud service for which event-based alarms are generated. Therefore, you need to create an alarm rule for each group within that cloud service. If resources are added to a resource group, you need to manually add the resources to the event alarm rule.

Create an event alarm rule and set the monitoring scope to all resources.

Event alarms do not require rights- and domain-based management.

-