Before Changes
- Silence/inhibit rules were matched during incident notification, intercepting notifications if matched
- Intercepted incidents generated interception records
After Changes
- Silence/inhibit rules are now matched during alert processing, preventing incident creation if matched
- Intercepted alerts will not trigger or merge into incidents
- You can choose to retain or drop intercepted alerts; retained alerts will generate interception records
- Intercepted alerts can be filtered in the console
Why This Change
When an incident aggregates multiple alerts, its labels may differ from the original alerts. Matching silence/inhibit rules at the incident level caused these issues:
- Unwanted alerts couldn't be intercepted when merged into valid incidents
- Valid alerts had notifications blocked when merged into silenced/inhibited incidents
- When silence period ended, alerts belonging to an open silenced/inhibited incident still had notifications blocked
- Intercepted incidents couldn't be filtered as interception status changed over time
Impact
- ❌ If you have active silence/inhibit rules:
- Intercepted alerts will be retained with silence/inhibit reasons recorded but won't generate incidents
- ✅ If you have no active silence/inhibit rules:
- No impact