Skip to content

Mute Management

You can manage the mute settings for all rules of different monitors, intelligent inspections, self-built inspections, SLOs, and alert strategies in the current workspace. The mute referred to here means: events that meet the mute rule will not send alert notifications, 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. Input the name of the mute rule, and optionally input a description of the rule;
  2. Select mute scope;
  3. Define mute time;
  4. Configure corresponding notification targets for the mute rule;
  5. Add additional information, marking the cause or source of the mute, etc., obtaining information from various monitoring scenarios from the perspective of actual business;
  6. Click save.

Mute Scope

It mainly includes four dimensions:

Select the monitoring rules you want to mute, including 【monitors】【intelligent monitoring】【intelligent inspection】【SLO】; multiple selections allowed. The selected monitoring rules will not send alert notifications during the mute period, but events will still be generated.

The monitoring rules associated with alert strategies will not send alert notifications during the mute period, but events will still be generated; multiple selections allowed.

Select tags; if the monitor belongs to the selected tags, it will be muted; multiple selections allowed.

Choose monitors to mute based on any dimension; multiple selections 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 for more information.

Advanced Filtering

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

Event attributes can be filtered through the fields provided by the dropdown list; you can also manually input key and value for binding.

The format of the filter condition is as follows: attribute:value, attribute:*value*, -attribute:value, -attribute:*value*. Different field combinations have an AND relationship, while multiple values of the same field have an OR relationship. You can freely combine AND and OR for different fields.

After entering the filter condition, there are several situations regarding tags:

Example:

Assume the premise is that the monitor exists grouped by host, service. In advanced filtering, we configure the filter condition host:cn-hangzhou AND service:guance. If both host:cn-hangzhou AND service:guance and host:cn-shanghai AND service:guance trigger thresholds and generate events simultaneously, then only host:cn-hangzhou AND service:guance will be muted, and host:cn-shanghai AND service:guance will still send alert notifications.

For more examples, refer to Understanding 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 for mute rules here.

You can customize the time zone, start time, and end time for alert muting, or 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, 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 the Mute Schedule in the top 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 the recipients clearly understand the detailed information of the mute rule. At the same time, you can set the exact time when the notification is triggered. 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 within the current workspace, including their mute scope, status information, mute type, repetition frequency, mute time, etc.

Three Mute States

Pending: Not yet at the effective time of the mute;

In Progress: Within the mute time range, matching events are in mute state and will not send external alert notifications;

Expired: The mute time is in the past, and the mute rule has become invalid.

You can manage the list via the following operations.

  • Search: Keyword search for related mute rules based on mute scope.

  • Settings: Adjust display columns, including rule name, status, mute scope, mute type, repetition, description, mute time;

  • Disable/Enable: Disabling or enabling mute rules generates operational audit events, which can be viewed under workspace Management > Audit Events.

    • Enable: Mute rules execute according to normal procedures;
    • Disable: Mute rules do not take effect; if a mute notification strategy is set and the choice 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;

  • Operation Audit: Click to jump and view operation records related to this mute rule;

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

  • Shortcut Filtering: Filter and sort based on five fields: status, whether enabled, mute type, creator, and updater.

Feedback

Is this page helpful? ×