Mute
Mute an incident that keeps coming back while you already know the cause, for example a noisy check during a planned migration. Oppex resolves the incident and, for the mute period, resolves matching new incidents as they arrive, without alerting anyone.
You can mute only an incident that is currently assigned to you and that belongs to a group. This rule is the same for every role. An incident belongs to a group when its Group Name, under More Details, is set.
Muting is not a notifications-only switch. It resolves this incident now. Until the mute ends, every new incident from the same service with the same group name is resolved as soon as it arrives, and nobody is paged. A mute cannot be lifted from the product. To end one early, contact Oppex support.
Mute an incident
- In the Incidents list, click ⋮ on the incident's row.
- Click Mute Incident. The Mute Incident dialog opens.
- Under Mute duration, select Hours (1 – 72 hours) or Days (1 – 7 days).
- Click − or + to set the duration. The default is 6 hours, and Mutes until shows when the mute ends.
- Click Mute. Oppex shows "Incident muted for 6 hours".
1 – 72 hours Days
1 – 7 days
The incident is resolved, and the timeline records who muted it and for how long. Each incident resolved by the mute records in its timeline that a similar incident was muted, by whom, and for how long.
Oppex adds a short root cause analysis (RCA) automatically, so that the incident can be resolved. You can replace it later with Update RCA. See Resolve.
Limits
| Rule | Detail |
|---|---|
| Longest mute | 7 days. There is no permanent mute. |
| What is matched | New incidents from the same service with the same group name |
| An active mute already exists for that service and group | Oppex keeps the existing mute and does not resolve this incident |
| Ending a mute early | Not available in the product. Contact Oppex support. |