Docs

Cloud Monitor

Event center

Event suppression

Frequent, low-severity event notifications from event rules can bury more important notifications. You can use event suppression to block this noise so you can focus on what really matters. This topic describes how to configure event suppression policies based on resource objects or event details.

Limits

If Suppression resource is set to All resources, no limit applies to the match rule quantity.

If Suppression resource is set to Partial resources, up to 10 match rules can be configured per suppression policy.

Each root user can have up to 1000 suppression policies at the same time.

Suppressing events by resource object

Background

You can implement event suppression based on monitored resource objects. You can suppress events for all resources or partial resources based on cloud products or event rules.

Procedure

In the left navigation bar, click Notification > Silence strategy.

On the Suppression policy page, click Create suppression policy.

On the Create suppression policy page, configure the event suppression policy.

Basic information

Parameter	Descriptions
Name	Specify a custom suppression policy name to identify this suppression policy. The name can contain special characters. The name cannot start with a digit, a hyphen (-), or other special characters. The name must be 1 to 128 characters in length.
Description	Provide a description of the suppression policy.

Silence strategy

Parameter	Descriptions
Suppression type	Select Alert policy or Event rule. In this scenario, select Event rule.
Event source	Select the Event source (cloud product) for event suppression.
Event rule	Select the event rule to be suppressed. If an event rule is specified, event notifications under the specified event rule and corresponding event source will be suppressed. If no event rule is specified, event notifications generated by resources from the event source will be suppressed.
Suppression event	Select the specific events to be suppressed.
Suppressed resource	Select the resource scope for suppression. You can select All resources or Partial resources to suppress events at the level of monitored resources. If you select Partial resources is selected, you can configure the relationship between match rules, including: Anyone is met: Individual rules have a logical OR relationship. Any match rule satisfied will trigger this suppression policy. All are met: Individual match rules have a logical AND relationship. All the specified rules must be satisfied to trigger this suppression policy. If you select Partial resources, resources can be matched based on tag keys and values of cloud resources. Supported resource tags include ResourceID, ResourceName, ResourceProject, Tag, and more. Supported tags may vary with cloud products. You can query the supported tags for a specific cloud product in the console. Supported matching methods include Prefix matches, Suffix matches, Contain, Not contain, Equal to, and Not equal to. You can specify multiple tag values. After you enter a tag value, press Enter to confirm it. You can enter up to 50 tag values, with each tag value not exceeding 128 characters in length.

Suppression time

Parameter	Descriptions
Effective time	You can specify one of the following suppression time options: Suppress permanently: No specific suppression time is required. As long as the suppression policy is effective, suppression is enabled. To disable suppression, stop the corresponding suppression policy. Suppression at absolute time: The suppression policy applies within the specified, fixed period of time. Suppression at relative time: The suppression applies periodically within the specified cycle.
Time range	If you select Suppression at absolute time for Effective period, configure the Time range for suppression. warning You can specify up to three time ranges. Available options include 3 hours, 6 hours, One day, This week, Next week, and Custom. If you select Custom, specify a Start date and End date.
Cyclic time type	If you select Suppression at relative time for Effective period, you also need to configure Cyclic time type for suppression. You can select Cycle permanently or Cycle in specified days. If you select Cycle permanently, specify the start time and end time for suppression. If you specify Cycle in specified days, specify a time range, suppression start time, and suppression end time. The time range options include This week, Next week, and Custom. If you select Custom, specify a Start date and End date.

Click Submit to complete the configuration.

Verifying results

After configuring an event suppression policy, you will not receive events for the corresponding resources during the specified suppression time. You can view suppressed events under the suppression policy on the Suppression history tab of the suppression policy details.

You can still view the corresponding events on the Cloud product event page.

Suppressing events based on event details

Background

You can use the fields in the data entry in the cloud product event details to implement more sophisticated event suppression policies. For example, you can implement event suppression based on the instance status or instance ID of a cloud product. Event details vary by cloud product. For details, see Querying events.

For example, you purchase ECS instances and GPU Compute Service instances, and integrate them with Cloud Monitor. During daily operation and maintenance, you need to focus on abnormal events triggered only by these GPU Compute Service instances. In this case, you can use the fields in the event details to suppress events related to non-GPU servers. The following is an example of event information about an ECS instance. The WithGPUDevice field indicates whether the instance has a GPU. When the value is false, the server does not have a GPU. This topic uses this field as an example to describe how to suppress events based on event fields.

{​
   "specversion": "1.0",​
    "id": "18943***",​
    "source": "ecs",​
    "type": "ecs:Instance:DeleteInstance.Succeeded",​
    "volcpublishtime": "2025-02-25T18:42:45+08:00",​
    "volcregion": "cn-beijing",​
    "volcaccountid": "2100***",​
    "volceventbusname": "default",​
    "volcresourcename": "auto***",​
    "resourceid": "i-ydq64***",​
    "subject": "ecs:cn-beijing:2100***:instance/i-ydq64***",​
    "datacontenttype": "application/json",​
    "time": "2025-02-25T18:42:44+08:00",​
    "data": {​
        "EventType": "DeleteInstance",​
        "PrivateIpAddress": [​
            "192.168.1.8"​
        ],​
        "EventStatus": "Succeeded",​
        "ExtraInfo": {},​
        "PublicIpAddress": [​
            "101.126.11.209"​
        ],​
        "HappenAt": "2025-02-25T18:42:44+08:00",​
        "InstanceId": "i-ydq64***",​
        "WithGPUDevice": false,​
        "EventId": "e-ydq65***",​
        "InstanceName": "auto***"​
     }​
}​

The following matching methods are supported for event suppression based on event details.

Matching method	Matching description	Matching example
Field	data.a	If you set data.WithGPUDevice to false, events with the field "WithGPUDevice": false will be matched.
Array	data.a[0]	If data.PrivateIpAddress[0] is set to 192.68.1.8, events with the field "PrivateIpAddress":["192.168.1.8"] will be matched. tip The * wildcard is supported for array-based matching. If you configure data.a[], any item in the data.a array will be matched. For example, if you configure data.PrivateIpAddress[], any item in the PrivateIpAddress array will be matched. If you configure data.a[*].b, you can continue to access nested fields even if a is a complex nested array.
Nesting	data.a.b[0].c	-

Procedure

In the left navigation bar, click Notification > Silence strategy.

On the Suppression policy page, click Create suppression policy.

On the Create suppression policy page, configure the event suppression policy.

Basic information

Parameter	Descriptions
Name	Specify a custom suppression policy name to identify this suppression policy. The name can contain special characters. The name cannot start with a digit, a hyphen (-), or other special characters. The name must be 1 to 128 characters in length.
Description	Provide a description of the suppression policy.

Silence strategy

Parameter	Descriptions
Suppression type	Select Alert policy or Event rule. In this scenario, select Event rule.
Event source	Select the Event source (cloud product) for event suppression.
Event rule	Select the event rule to be suppressed. If an event rule is specified, event notifications under the specified event rule and corresponding event source will be suppressed. If no event rule is specified, event notifications generated by resources from the event source will be suppressed.
Suppression event	Select the specific events to be suppressed.
Suppressed resource	Select the resource scope for suppression. If you select Event details, event suppression is implemented based on fields in the event details. You can use fields, arrays, or nested structures in the data entry of the cloud product event to suppress events. In this example, the resource for suppression is data.WithGPUDevice, the condition is equals, and the value is false. This means that all events related to non-GPU ECS instances are suppressed. tip For supported fields and matching methods in suppression policies, see Background information. You can configure the relationship between match rules, including: Anyone is met: Individual rules have a logical OR relationship. Any match rule satisfied will trigger this suppression policy. All are met: Individual match rules have a logical AND relationship. All the specified rules must be satisfied to trigger this suppression policy. Matching can be based on field keys and values in the event. Each field supports one value, which cannot exceed 128 characters in length. Supported matching methods include Prefix matches, Suffix matches, Contain, Not contain, Equal to, and Not equal to.

Suppression time

Parameter	Descriptions
Effective time	You can specify one of the following suppression time options: Suppress permanently: No specific suppression time is required. As long as the suppression policy is effective, suppression is enabled. To disable suppression, stop the corresponding suppression policy. Suppression at absolute time: The suppression policy applies within the specified, fixed period of time. Suppression at relative time: The suppression applies periodically within the specified cycle.
Time range	If you select Suppression at absolute time for Effective period, configure the Time range for suppression. warning You can specify up to three time ranges. Available options include 3 hours, 6 hours, One day, This week, Next week, and Custom. If you select Custom, specify a Start date and End date.
Cyclic time type	If you select Suppression at relative time for Effective period, you also need to configure Cyclic time type for suppression. You can select Cycle permanently or Cycle in specified days. If you select Cycle permanently, specify the start time and end time for suppression. If you specify Cycle in specified days, specify a time range, suppression start time, and suppression end time. The time range options include This week, Next week, and Custom. If you select Custom, specify a Start date and End date.

Click Submit to complete the configuration.

Verifying results

You can still view the corresponding events on the Cloud product event page.

Last updated: 2026.07.10 14:02:24