Silence a Firing Alert

Silence a Firing Alert

Create a silence for a firing alert and verify it is suppressed.

1. Locate the firing alert and capture the label set Alertmanager is actually holding for it. The fingerprint identifies this unique label combination.
2. List the configured receivers so the operator can record which notification integrations this silence is about to mute.
3. Create the silence. Every matcher must match for an alert to be suppressed, so alertname plus instance scopes this to the one firing target and leaves the same alert on other instances still paging.
4. Read the silence back by its id and check its state. A state of pending means startsAt is in the future and the alert will keep paging until then.
5. Re-read the alert including silenced alerts and confirm Alertmanager now reports it suppressed and attributes the suppression to this silence.

What you'll need to have ready

• alertName: The alertname label value to silence (e.g. HighRequestLatency).
• alertNameMatcher: The alert expressed as a label matcher for filtering (e.g. alertname="HighRequestLatency").
• instance: The instance label value to scope the silence to a single target rather than every instance of the alert.
• startsAt: When the silence takes effect, as an RFC3339 timestamp.
• endsAt: When the silence expires, as an RFC3339 timestamp. Always set this to a real bound so the silence cannot outlive the incident.
• createdBy: The person or system creating the silence.
• comment: The reason for the silence, including a ticket reference.

For your developer

Arazzo workflow prometheus:silence-firing-alert, 5 operations: getAlerts → listReceivers → createSilence → getSilence → getAlerts. Specs on APIs.io.