Skip to content

Mute Management

You can manage muting for all rules of different Monitors, Intelligent Inspection, Custom Inspection, 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 enabled, 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, as needed, 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 mute, so as to obtain information about various monitoring scenarios from an actual business perspective;
  6. Save.

Mute Scope

It mainly covers four dimensions:

Select the monitoring rules to mute, including [Monitor], [Smart Monitoring], [Intelligent Inspection], [SLO]; multiple selections are supported. The selected monitoring rules will not send alert notifications during the mute period, but events will still be generated.

Monitoring rules associated with the alert policies will not send alert notifications during the mute period, but events will still be generated; multiple selections are supported.

Select tags; if a monitor belongs to a selected tag, it will be muted; multiple selections are supported.

Select the monitors to mute based on any dimension; multiple selections are supported;
You can select related Monitors, Intelligent Inspection, Custom Inspection, SLOs, and Alert Policies as mute targets. Click to jump to the details page for more information.

Effective Scope

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

By default, it only takes effect on events. You can enable "Also mute incidents". After enabling, the mute rule also applies to incident notifications, and incidents matching the scope will no longer trigger any notifications.

Advanced Filtering

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

Go to Monitoring > 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, or manually enter event fields. Field names and values can be viewed in Event Details.

The filter condition format is 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 has by host,service grouping. 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 thresholds and generate events at the same time, only host:cn-hangzhou AND service:gc will be muted, while host:cn-shanghai AND service:gc will still send alert notifications.

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

Mute Time

That is, alert messages will not be sent within the configured time range.

Note

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

You can customize the time zone, start time, and end time for alert muting, and 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 time, including by day, by week, and by month;
  4. Select the end time of the mute, that is, the expiration time. You can choose to repeat forever according to the above schedule or repeat until a specific time.

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

Notification Targets

When configuring a mute rule, you can specify notification targets and customize the notification content so that recipients can clearly understand the specifics of the mute rule. You can also set the time when the notification is triggered, including immediately after the mute rule takes effect, or 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, recurrence frequency, mute time, and so on.

Three Mute Statuses

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

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

  • Expired: The mute time has passed and the mute rule is no longer effective.

You can manage the list with the following actions:

  • Search: Search related mute rules by keywords 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, which can be viewed in the workspace under Manage > Audit Events:

    • Enable: The mute rule executes as normal;
    • Disable: The mute rule does not take effect; if a mute notification policy is configured with "xx minutes before start" and the mute notification action has not been executed yet, the notification will not be executed.

  • Edit: Re-edit the mute rule;

  • 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 alerting;

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

Feedback

Is this page helpful?