Expire a Silence Early

Expire a Silence Early

Expire an active silence and verify the alert can fire again.

1. List the silences whose matchers cover this label matcher and take the first. Silences in the expired state are still returned here, which is why the next step checks the state before expiring anything.
2. Read the silence in full before lifting it. The comment and createdBy fields are what confirm this is the silence from this incident and not a long-standing maintenance window someone else owns.
3. Expire the silence by setting its end time to now. Alerts matching it resume notifying on the next Alertmanager evaluation.
4. Read the silence back and confirm its state is now expired rather than active or pending.

What you'll need to have ready

• silenceMatcher: Label matcher identifying the silence to lift (e.g. alertname="HighRequestLatency").

For your developer

Arazzo workflow prometheus:expire-silence, 4 operations: listSilences → getSilence → deleteSilence → getSilence. Specs on APIs.io.