Skip to content

Mute Management

You can manage muting for all rules of different monitors, intelligent inspections, custom inspections, SLOs, and alert policies in the current workspace. Muting here means: Events that match the mute rule do not send alert notifications, SLOs are not counted toward score deductions, but event data is still generated. After muting is set, the muted objects do not send alert notifications to any alert notification targets during the mute time.

Create

  1. Enter a name for the mute rule, and optionally a description for 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 reason or source of the muting, so as to obtain information about various monitoring scenarios from the perspective of actual business;
  6. Save.

Mute Scope

It mainly includes four dimensions:

Select the monitoring rules to mute, including Monitor, Smart Monitoring, Intelligent Inspection, and SLO; multiple selection is supported. The selected monitoring rules do not send alert notifications during the mute time, but events are still generated.

Monitoring rules associated with the alert policies do not send alert notifications during the mute time, but events are still generated; multiple selection is supported.

Select tags. Monitors that belong to the selected tags are muted; multiple selection is supported.

Select monitors to mute based on any dimension; multiple selection is supported;
You can select related monitors, intelligent inspections, custom inspections, SLOs, and alert policies as mute objects. Click to jump to the details page to view the details.

Effective Scope

When the mute scope is "Based on Monitoring Rules", "Based on Monitor Tags", or "Custom", you can configure the effective scope.

By default, the rule applies to events only. You can enable "Also mute incidents". After it is enabled, the mute rule also applies to incident notifications, and incidents generated within the matching scope will no longer trigger any notifications.

Advanced Filtering

Use event attributes to further limit the mute scope, for example, to mute only events from a specified service or environment.

Go to Monitors > Mute Management. In Mute Scope > Advanced Filtering when creating or editing a rule, select common fields such as host, Kubernetes, and application service, and set matching values. You can also manually enter event fields. Field names and values can be viewed in Event Details.

Filter conditions are formatted as follows: attribute:value, attribute:*value*, -attribute:value, -attribute:*value*. Different fields are matched by AND, and multiple values for the same field are matched by OR.

After entering filter conditions, the following cases apply to tags:

Example:

Assume that the monitor is grouped by host, service. In Advanced Filtering, we configure the filter condition host:cn-hangzhou AND service:gc. If the monitored objects of both combinations host:cn-hangzhou AND service:gc and host:cn-shanghai AND service:gc trigger thresholds and generate events at the same time, only host:cn-hangzhou AND service:gc is muted, while host:cn-shanghai AND service:gc still sends alert notifications.

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

Mute Time

That is, no alert notifications will be sent within the configured time range.

Note

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

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

  1. Select the time zone;
  2. Select the mute start time and duration;
  3. Select the mute recurrence period after a certain time, including by day, by week, and by month;
  4. Select the mute end time, that is, the expiration time. You can choose to repeat according to the above schedule forever 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 clearly understand the specific information of the mute rule. You can also set the specific time when the notification is triggered, including 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, mute type, recurrence frequency, mute time, and other information.

Three mute statuses

  • Pending: The mute effective time has not yet been reached;

  • In progress: Within the mute time range, matched events are in a muted state and do not send alert notifications;

  • Expired: The mute time is in the past, and the mute rule is no longer effective.

You can manage the list with the following operations:

  • Search: Search for related mute rules by keyword in the mute scope;

  • Settings: Adjust the displayed columns, including rule name, status, mute scope, mute type, recurrence, description, and mute time;

  • Disable/Enable: Disabling or enabling a mute rule generates audit events. You can go to Manage > Audit Events in the workspace to view them:

    • Enable: The mute rule runs according to the normal process;
    • Disable: The mute rule does not take effect. If a mute notification policy is configured, the option "xx minutes before start" is selected, and the mute notification action has not yet been executed, the notification will not be sent.

  • Edit: Re-edit the mute task;

  • Clone the mute rule;

  • Operation audit: Click to jump to view the operation records related to this mute rule;

  • Delete: The deleted mute scope will resume its alerting status;

  • Quick filter: Filter by five fields: status, whether enabled, mute type, creator, and updater.