Yandex Cloud
Search
Contact UsTry it for free
  • Customer Stories
  • Documentation
  • Blog
  • All Services
  • System Status
  • Marketplace
    • Featured
    • Infrastructure & Network
    • Data Platform
    • AI for business
    • Security
    • DevOps tools
    • Serverless
    • Monitoring & Resources
  • All Solutions
    • By industry
    • By use case
    • Economics and Pricing
    • Security
    • Technical Support
    • Start testing with double trial credits
    • Cloud credits to scale your IT product
    • Gateway to Russia
    • Cloud for Startups
    • Center for Technologies and Society
    • Yandex Cloud Partner program
    • Price calculator
    • Pricing plans
  • Customer Stories
  • Documentation
  • Blog
© 2026 Direct Cursus Technology L.L.C.
Monium
  • Getting started
  • Overview
    • Mutes
  • Access management
  • Pricing policy
  • Terraform reference
  • Release notes

In this article:

  • Mute parameters
  • Examples of mute selectors
  • Mute states
  • Interaction between mutes and escalations
  1. Alerts
  2. Mutes

Mutes

Written by
Yandex Cloud
Updated at February 4, 2026
  • Mute parameters
  • Examples of mute selectors
  • Mute states
  • Interaction between mutes and escalations

Mutes allow you to temporarily disable notifications from a specific alert or group of alerts. Mutes do not affect the alert calculation process; the relevant status will be shown in the interface.

Mutes remain active for a specified period, then get turned off and, 7 days later, deleted by TTL.

Mute parametersMute parameters

  • Mute period: Mute start and end date and time.
  • Name: Mute name.
  • Description: Description of the reasons for adding the mute.
  • Selector: Selector used to search for muted alerts.

Available labels for alert search:

  • alert.id and sub_alert.id: Alert ID.
  • alert.name: Alert name.
  • alert.labels.LABEL_NAME: Alert labels.
  • sub_alert.labels.LABEL_NAME: Multialert breakdown labels.

The selector supports glob expressions, e.g., alert.id='*prod-???'. You can specify multiple labels for a more accurate search, e.g., alert.id='*-prod', alert.labels.serviceProviderId=compute.

Note

The input field will autosuggest the alert labels and multialert breakdown labels available in the project.

When creating or editing a mute, you can see which alerts match the mute selectors under Alerts that will be muted.

Examples of mute selectorsExamples of mute selectors

  • Mute by alert ID:
    alert.id='test_alert'
    
  • Mute all alerts by ID template:
    alert.id='test_alert*'
    
  • Mute all alerts by name template:
    alert.name='*query*|*product*'
    
  • Mute subalert by ID:
    sub_alert.id='500f279065221ba31a4feb9319b24eb2bd42c4ac'
    

Mute statesMute states

Depending on its settings and current time, a mute can switch between the following states:

  • Pending: The mute has been scheduled but is not affecting any alerts yet.

  • Active: The mute is active and it mutes all messages from alerts and sub-alerts covered by its selectors.

  • Expired: The mute has expired and is no longer affecting any alerts.

  • Archived: The mute expired more than a day ago.

Pending, Active, and Expired mutes are shown in a special section on the status pages of linked alerts and sub-alerts. Archived mutes are not considered linked with any alerts, even if the alert ID is covered by the mute's selector. These mutes are stored for historical reasons and are deleted by TTL in six days after switching to the Archived status.

Alert

In a day after a mute expires, it switches to the Archived status. In six days after it switches to the status, the mute is deleted permanently.

Interaction between mutes and escalationsInteraction between mutes and escalations

If you configure a mute for a Monium alert, escalation will not start.

Was the article helpful?

Previous
Escalations
Next
Overview
© 2026 Direct Cursus Technology L.L.C.