Application Real-Time Monitoring Service:Create and manage a silence policy

Create a silence policy

1. Log on to the ARMS console. In the left-side navigation pane, choose Alert Management > Silence Policies.

2. On the Silence Policies page, click Create Silence Policy.

3. On the Create Silence Policy page, set Silence Policy Name.

4. In the Silent Event Matching Rule section, configure the matching rules for silence events.

   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. For more information, see Create and manage a notification policy.

   1. Select the data source.

      • If you specify a data source, the policy applies to the alert events from the specified source (integrated component).

      • If you do not specify a data source, the policy applies to all alert events.

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

      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 that are provided by ARMS. The following table describes the default tags.

        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. For more information, see Namespaces in Kubernetes documentation.
        	pod_name	The name of the Pod. For more information, see Pods in Kubernetes documentation.
        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.

5. Set Effective Period. The options are as follows:

   • 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 to specify the time period.

6. Click Save.

Manage a silence policy

On the Silence Policies page, you can:

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

• Enable or disable a silence policy: In the Status column of the policy, turn the switch on or off.

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

• Copy a silence policy: Click Copy in the Actions column of the policy to create an identical one.