Skip to content

Mute Management

You can manage mute rules for all rules of different 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 up 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, etc., to obtain information from various monitoring scenarios from a practical business perspective.
  6. Save.

Mute Scope

It mainly includes four dimensions:

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

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

Select tags. 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 relevant monitors, intelligent inspections, self-built inspections, SLOs, and alert strategies as mute objects. Click to jump to the details page to view details.

Advanced Filtering

The detection results of monitoring rules are recorded as events. All attribute fields of events can be used as filter conditions to further filter the mute scope.

Event attributes can be filtered by tags through the fields provided in the dropdown list. You can also manually enter key and 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 for the same field are OR. You can freely combine AND and OR for different fields.

After entering the filter conditions, the following situations exist for tags:

Example:

Assume the premise is that the monitor has grouping by host and service. In advanced filtering, we configure the filter condition host:cn-hangzhou AND service:gc. If the detection objects of both combinations host:cn-hangzhou AND service:gc and host:cn-shanghai AND service:gc trigger the threshold and generate events at the same time, 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, please refer to How to understand event attributes in mute rules.

Mute Time

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

Note

Adjusting the global time zone does not affect the mute time set for mute rules here.

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

  1. Select the time zone.
  2. Select the start time and duration of the mute.
  3. Select the mute cycle starting from a certain moment, including daily, weekly, and monthly.
  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 Schedule 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. You can also set the specific time for notification triggering. This includes sending immediately after the mute rule takes effect or sending 15 minutes, 30 minutes, or 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, matched events are in a muted 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, and mute time.
  • Disable/Enable: Disabling or enabling mute rules will generate audit events. You can go to workspace Management > Audit Events to view:
    • 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 "xx minutes" before the start is selected and the mute notification operation has not been executed yet, the notification will not be executed.
  • Edit: Re-edit the mute task.
  • Clone mute rule.
  • Operation Audit: Click to jump to view operation records related to this mute rule.
  • Delete: The deleted mute scope will resume the alert state.
  • Quick Filter: Filter based on five fields: status, enabled or not, mute type, creator, and updater.

Feedback

Is this page helpful? ×