# Silences page

## Overview

The Silences page lists all Silences you and your team created for your Monitors. In this section, you can also create and manage your Silence rules, to suppress notifications and Issues noise, for a specified period of time. Silences are a great way to reduce alert fatigue, which can lead to missing important issues, and help focus on the most critical issues during specific operational scenarios such as scheduled maintenances.

## Create a new Silence

Follow these simple steps to create a new Silence.

<figure><img src="https://2771001740-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FUHgqKYgCiRKdOpWQdi52%2Fuploads%2Fgit-blob-a137888784e315eaa794a042589a24510c35e1e9%2Fimage.png?alt=media" alt=""><figcaption></figcaption></figure>

### Section 1: Schedule

Specify the timeframe for the silence rule. Note that the starting point doesn't have to be now, and can also be any time in the future.

Below the From / Until boxes, you'll see a Silence summary, showing its approximate length (rounded down to full days) and starting date.

### Section 2: Matchers

Define the criteria for Monitors or Issues to be silenced.

1. Click **Add Matcher** to specify match conditions (e.g., cluster, namespace, span\_name).
2. Combine multiple matchers for more granular control.

**Example:** Silence all Monitors in the "demo" namespace.

### Section 3 - Affected Active Issues

Preview the issues currently affected by the Silence rule, based on any defined Matchers. This list contains only actively firing Issues.

**Tip:** Us this preview to see the list of impacted issues and adjust your Matchers before finishing to create the Silence.

### Section 4: Comment

Add notes or context for the Silence rule. These comments help you and other users understand the purpose of the rule.