Skip to content

Mute Management

You can manage mute rules for all monitors, intelligent inspections, self-built inspections, SLOs, and alert strategies in the current workspace. Mute here means: Events that meet the mute rules will not send alert notifications, SLOs will not be deducted, but event data will still be generated. After setting the mute, the muted objects will not send alert notifications to any alert notification targets during the mute period.

Create

  1. Enter the name of the mute rule and optionally enter a description of the rule.
  2. Select the Mute Scope.
  3. Define the Mute Time.
  4. Configure the corresponding Notification Targets for the mute rule.
  5. Add additional information to identify the cause or source of the mute, and obtain information from various monitoring scenarios from a practical business perspective.
  6. Click Save.

Mute Scope

Mainly includes four dimensions:

Select the monitoring rules to be muted, including [Monitors], [Intelligent Monitoring], [Intelligent Inspection], [SLO]. Multiple selections are allowed. The selected monitoring rules will not send alert notifications during the mute period, but events will still be generated.

Monitoring rules associated with alert strategies will not send alert notifications during the mute period, but events will still be generated. Multiple selections are allowed.

Select tags, and monitors belonging to the selected tags will be muted. Multiple selections are allowed.

Select monitors to be muted based on any dimension. Multiple selections are allowed.
You can select related monitors, intelligent inspections, self-built inspections, SLOs, and alert strategies as mute objects, and click to jump to the details page to view details.

Advanced Filtering

The detection results of monitoring rules will be recorded as events, and all event attribute fields can be used as filtering conditions to further filter the mute scope.

Event attributes can be filtered by tags provided in the dropdown list. You can also manually enter key, value for binding.

The filter condition format is as follows: attribute:value, attribute:*value*, -attribute:value, -attribute:*value*, the combination relationship between different fields is AND, and multiple values of the same field are OR. You can freely combine AND and OR for different fields.

After entering the filter conditions, there are several situations for tags:

Example:

Assuming the premise is that the monitor has by host,service grouping. In the advanced filter, we configure the filter condition host:cn-hangzhou AND service:gc. If both host:cn-hangzhou AND service:gc and host:cn-shanghai AND service:gc trigger the threshold and generate events, then only host:cn-hangzhou AND service:gc will be muted, and host:cn-shanghai AND service:gc will still send alert notifications.

For more examples, refer to How to Understand Event Attributes in Mute Rules.

Mute Time

That is, no alert information will be sent within the set time range.

Note

Adjusting the Global Time Zone does not affect the mute time set here.

You can customize the time zone, start time, and end time for the alert mute, and you can also quickly set it to 1 hour, 6 hours, 12 hours, 1 day, 1 week.

  1. Select the time zone.
  2. Select the start time and duration of the mute.
  3. Select the mute cycle from a certain moment, including by day, by week, by month.
  4. Select the end time of the mute, i.e., the expiration time. You can choose to repeat forever according to the above time or repeat until a specific moment.

Click Mute Plan in the upper right corner to preview the current mute time configuration.

Notification Targets

When configuring the current mute rule, you can specify notification targets and customize the notification content so that recipients can clearly understand the specific information of the mute rule. At the same time, you can also set the specific time for the notification to trigger. Including sending immediately after the mute rule takes effect or sending 15 minutes, 30 minutes, 1 hour before the mute starts.

Manage Rules

In the mute rule list, you can view all mute rules in the current workspace, including their mute scope, status information, mute type, repeat frequency, mute time, and other information.

Three Mute Statuses

  • Pending: The mute effective time has not yet arrived.

  • In Progress: Within the mute time range, events that match are in a mute state and will not send alert notifications externally.

  • Expired: The mute time is in the past, and the mute rule has expired.

You can manage the list through the following operations:

  • Search: Search for related mute rules based on keywords in the mute scope.

  • Settings: Adjust the displayed columns, including rule name, status, mute scope, mute type, repeat, description, mute time.

  • Disable/Enable: Disabling or enabling mute rules will generate operation audit events, which can be viewed in the workspace Management > Operation Audit.

    • Enable: The mute rule is executed according to the normal process.
    • Disable: The mute rule does not take effect. If a mute notification strategy is set and the selected notification is "xx minutes" before the start and the mute notification operation has not been executed, the notification will not be executed.

  • Edit: Re-edit the mute task.

  • Clone Mute Rule.

  • Operation Audit: Click to jump to view the operation records related to this mute rule.

  • Delete: The deleted mute scope will restore the alert state.

  • Quick Filter: Filter based on status, whether enabled, mute type, creator, and updater.