# Suppression Rules Copy as Markdown[Open in ChatGPT](https://chatgpt.com/?q=Read%20https%3A%2F%2Fdocs-docusaurus.kinsta.page%2Fuser-guides%2Falerting%2Falert-suppression-rules.md%20and%20help%20me%20with%20my%20question%20about%20this%20Coralogix%20documentation%20page.)[Open in Claude](https://claude.ai/new?q=Read%20https%3A%2F%2Fdocs-docusaurus.kinsta.page%2Fuser-guides%2Falerting%2Falert-suppression-rules.md%20and%20help%20me%20with%20my%20question%20about%20this%20Coralogix%20documentation%20page.)[Terraform](https://registry.terraform.io/providers/coralogix/coralogix/latest/docs/resources/alerts_scheduler) Use **Suppression Rules** to mute alert notifications during scheduled maintenance, testing, auto-scaling events, or outside working hours. Note This feature is available for early-access customers. To request access and confirm your organization meets the feature criteria, contact your account representative or Support. ## How suppression rules work[​](#how-suppression-rules-work "Direct link to How suppression rules work") Suppression Rules automatically mute alerts according to parameters you define. You set what to suppress (which `key:value` attributes), when to suppress (a one-time or recurring time window), and which alerts the rule applies to. Note Suppression Rules disable notifications, not alert evaluation. A suppressed alert keeps evaluating, but no notification is sent and no Case is created. To stop an alert from evaluating entirely, disable the alert definition instead. Start from a preset to configure a rule with minimal effort: * **Scheduled maintenance**: suppress alerts during planned maintenance windows so routine work doesn't trigger notifications. * **Whitelisting**: exempt specific conditions or sources from alerting while keeping the rest of your alerts active. * **Working hours**: suppress alerts outside working hours so your team is notified only when it matters. * **System upgrade**: suppress alerts temporarily while you run an upgrade. * **Blank rule**: start from scratch and configure every field yourself. [![Suppression Rules page showing preset cards and a table of existing rules](/assets/images/suppression-rules-overview-f7084895908f1485bb794582e93256a3.webp)](https://docs-docusaurus.kinsta.page/assets/images/suppression-rules-overview-f7084895908f1485bb794582e93256a3.webp) Shows the Suppression Rules page with the preset cards and the rules table. ## Create a suppression rule[​](#create-a-suppression-rule "Direct link to Create a suppression rule") 1 . Go to **Alerts**, then **Suppression Rules**. 2 . Select **Create rule** in the top-right corner, or select a preset card to start from a template. 3 . Enter a **Name**. Optionally add a **Description** and one or more **Labels**. Labels are metadata you can use to filter and organize your rules. [![New suppression rule drawer with the rule fields and the matching alerts panel](/assets/images/suppression-rule-form-3dec1bd23f5cc4b985db16b26b8b8c2f.webp)](https://docs-docusaurus.kinsta.page/assets/images/suppression-rule-form-3dec1bd23f5cc4b985db16b26b8b8c2f.webp) Shows the suppression rule form alongside the matching alerts panel. ### Select what to suppress[​](#select-what-to-suppress "Direct link to Select what to suppress") 4 . Under **What to suppress**, select an attribute and enter one or more values to match. * Select **Add attribute** to match on more keys. When you set multiple attributes, an alert must contain all of them for the rule to apply. * When you set multiple values for one attribute, the rule suppresses alerts matching any of those values. * For attributes in IP-address format, enter an address range in CIDR notation to suppress every alert originating from that range. * To suppress all matching alerts regardless of attribute values, enable **Mute all system**. This suppresses every selected alert during the time window, including alerts set to notify immediately and alerts without a group-by key. ### Select whether to suppress or trigger[​](#select-whether-to-suppress-or-trigger "Direct link to Select whether to suppress or trigger") 5 . Under **Rule operation**, select **Suppress** to mute matching alerts during the period, or **Trigger** to send matching alerts only during the period. ### Set the time window[​](#set-the-time-window "Direct link to Set the time window") 6 . Under **Rule period**, select **One time** or **Recurring**, then set the schedule. * For **One time**, set a **Starting** date and time, then set the **Ending** point as either an end **Date** or a **Duration**. * For **Recurring**, select a **Schedule** of **Specific time** or **Always**, set the recurrence interval under **Recurring every**, then end it with a **Duration** or a termination date. 7 . Optionally set a **Timezone**. The rule uses your local time by default. ### Select which alerts the rule applies to[​](#select-which-alerts-the-rule-applies-to "Direct link to Select which alerts the rule applies to") 8 . In the **Matching alerts** panel, search the alert definitions by name and select the alerts to include. The panel previews which alerts match your current selector criteria. * To apply the rule to all current and future alerts, enable **Mute all system alerts and future alerts**. 9 . Select **Create rule** to save. Use the **Active** toggle to enable or disable the rule when you save it. ## Manage suppression rules[​](#manage-suppression-rules "Direct link to Manage suppression rules") The Suppression Rules table lists every rule with its name, status, labels, muted values, affected alerts, start and end time, type, and whether it is enabled. Filter the list by status, label, or free text, and use the **Enabled** toggle to turn a rule on or off without opening it. ### Edit, clone, or delete a rule[​](#edit-clone-or-delete-a-rule "Direct link to Edit, clone, or delete a rule") 1 . Open the more actions menu at the end of the rule's row. 2 . Select the action you want to perform: * **Edit**: change the rule, then select **Save changes**. * **Clone**: duplicate the rule, adjust it, then select **Save changes**. * **Delete**: remove the rule, then confirm. ## Related resources[​](#related-resources "Direct link to Related resources") [Getting started with alerts](https://docs-docusaurus.kinsta.page/user-guides/alerting/introduction-to-alerts/.md)[Cases](https://docs-docusaurus.kinsta.page/user-guides/cases/overview/.md)[Alert aggregation](https://docs-docusaurus.kinsta.page/user-guides/alerting/alert-aggregation/.md)[Notification Center](https://docs-docusaurus.kinsta.page/user-guides/notification-center/introduction/.md)