Managed Service for OpenTelemetry:Silence policies

Create a silence policy

1. Log on to the Managed Service for OpenTelemetry console. In the left-side navigation pane, choose Alert Management > Alarm policy.

2. Click the Silence Policies tab. On the tab page that appears, click Create Silence Policy on the right.

3. On the creation page, enter a name for the silence policy. In the Silent Event Matching Rule section, configure the rules for silencing alerts.

   Important

   Silence policies take precedence over notification policies: Alert events that match a silence policy are silenced and cannot be matched by a notification policy.

   1. Select a data source.

      • If you specify a source for alert events, the silence policy will filter alerts from the designated source using configured matching rules.

      • If you select No Preset Source, the silence policy will filter all alerts using configured matching rules.

   2. Specify one or more expressions. You can select existing tags and add custom ones.

      The following tags are available:

      • The fields that are included in an alert rule expression. For information about how to create a tag for an alert rule in Managed Service for Prometheus, see Create an alert rule for a Prometheus instance.

      • The default tags provided by ARMS, described below:

        Category	Tag	Description
        Common fields	alertname	The name of the alert.
        	clustername	The name of the Kubernetes cluster.
        	severity	The severity level of the alert. Valid values: P1 P2 P3 P4 Default
        	namespace	The name of the namespace.
        	pod_name	The name of the pod.
        Preset system fields	_aliyun_arms_integration_name	The name of the integration that you specified as the data source. By default, ARMS returns the integration name ARMS-DEFAULT.
        	_aliyun_arms_involvedObject_id	The ID of the object that triggers the alert.
        	_aliyun_arms_involvedObject_name	The name of the object that triggers the alert.
        	_aliyun_arms_region_id	The region ID of ARMS.
        	_aliyun_arms_alert_rule_id	The ID of the alert rule.
        	_aliyun_arms_alert_type	The type of the alert rule. Valid values: 101: Prometheus alert 5: Application Monitoring alert 4: Browser Monitoring alert

      Note

      • If you want an alert to be triggered when multiple conditions are met at the same time, click + Add Condition to add a matching condition in the same matching rule.

      • If you want an alert to be triggered when only a single condition is met, click + Add Rule to add a matching rule.

      Note

      • If you want an alert to be triggered when multiple conditions are met at the same time, click + Add Condition to add a matching condition in the same matching rule.

      • If you want an alert to be triggered when only a single condition is met, click + Add Rule to add a matching rule.

4. Set the time for the silence policy to take effect.Valid values:

   • Persistent: The policy is always effective.

   • Recurring: The policy takes effect on a daily or weekly basis. Select Every Day or Weekly and click Create.

   • Custom Time Period: Click Create and customize the time period.

5. Click Save.

Manage silence policies

On the Silence Policies tab, you can perform the following actions:

• Edit: Click a policy name or click Edit in the Actions column. In the panel that appears, change the settings and click Save.

• Enable or disable: Turn the switch on or off in the Status column.

• Delete: Click Delete in the Actions column. In the dialog box that appears, click OK.

• Copy: Click Copy in the Actions column to create an identical one.