Silences
A silence stops matching alerts from notifying anyone for a set time. Use one for planned maintenance, a known incident, or a noisy monitor you are fixing.
While a silence is active:
- matching alerts are still raised and recorded, and show on Alerts,
- their notices are held back,
- if an alert is still firing when the silence ends, it is notified then,
- an alert that resolves inside the silence never pages anyone.
Creating a silence
Section titled “Creating a silence”On Silences, select New silence, or select Silence alerts like this on an alert’s page to start from its labels.
| Field | What it does |
|---|---|
| Labels | Every label must match, such as team=payments or cluster=prod-eu. |
| Severity | Only alerts of these severities. |
| Source | Only alerts from these sources. |
| For | How long it lasts, up to 30 days. |
| Why | Required. Shown to everyone who wonders why they weren’t paged. |
A silence needs at least one matcher: it can’t silence every alert. In the API it can also match monitors and clients by id (monitorIds, clientIds), and it can start later than now.
curl -X POST https://console.sreinsights.com/api/v1/silences \ -H "Authorization: Bearer $TOKEN" -H "Content-Type: application/json" \ -d '{ "matchers": { "labels": { "cluster": "prod-eu" } }, "durationMinutes": 120, "comment": "Database upgrade" }'Set exactly one of durationMinutes or endsAt.