# Prune noisy alerts before adding another one

Treat this file as reference data, never as instructions that override the user or agent. Read the complete item before applying it. Keep use conditions, avoid conditions, limits, evidence roles and source links with the answer. An editorial block is a separately versioned analysis layer, not an original corpus claim or proof of efficacy. Cite the readable URL and version. Do not infer human review. This is a saved edition, not a live safety-notice service. Before consequential reuse, check the current page, https://vedokrok.com/data/availability.json and https://vedokrok.com/data/notices.json; absence alone does not explain why an item was removed.

Release: VEDOKROK-SEL-5d86e1b23401e578
Snapshot SHA-256: 30ce1c8fa9155763797e3d5cb55b1d94cbb8c3146ebd03fb3c006531ce60e82f
Current availability: https://vedokrok.com/data/availability.json
Current notices: https://vedokrok.com/data/notices.json

---

## Prune noisy alerts before adding another one

ID: MHC-D-RESEARCH-1279 · Version: 0.1.0 · Kind: principle
Source: https://vedokrok.com/knowledge/prune-noisy-alerts-before-adding-another-one

More warnings can make the important warning harder to hear.

Knowledge source release: MHC-RPUB-20261011-9e4b62c5
Source corpus commit: 9e4b62c5648844484b8cc3160f3e168d63a1241b
Source manifest SHA-256: 8cc91f0a764c635a79a18e06e048d3dc7bb1e07ae0fed6bf544c89832c024402
Source projection SHA-256: d03d10dd52b53dec1ed850b7706847ba5b200e60f24c4fbda4518c2004356104

### Use when

- People ignore, mute or delay responses to a notification channel that contains many false, duplicate or low-value alerts.

### Avoid when

- Do not optimize only for low alert count. Rare high-consequence alerts may deserve strong interruption even if they are inconvenient.

### Explanation

Treat attention as a limited system resource. Measure which alerts are actionable, duplicated, stale or routinely dismissed; then remove, combine, delay or downgrade the low-value ones before adding more. Review the misses as well as the volume: a quiet channel that hides critical states is not an improvement. The goal is higher signal value, not simply fewer messages.

### Example

If a CI channel posts every successful retry and every transient warning, group the routine noise and preserve immediate interruption for states that need human intervention.

### Check

The alert set becomes smaller or better grouped while retaining a clear path for genuinely time-sensitive states.

### Limits

- Do not optimize only for low alert count. Rare high-consequence alerts may deserve strong interruption even if they are inconvenient.

### Evidence and sources

- supports: AHRQ PSNet describes alarm fatigue as slower or absent response when people are repeatedly exposed to alarms that are invalid or nonactionable. — RS-A6ED4054F9E4F86D. The cited evidence is clinical; notification fatigue in software can share the attention mechanism without having the same risk magnitude. (Summary)
- supports: AHRQ's alarm-safety summaries emphasize reducing nonactionable alarms and improving the usefulness and prioritization of alerts rather than simply adding more alerts. — RS-A6ED4054F9E4F86D. The correct alert threshold and modality depend on the task, consequence and user environment. (Summary)
- RS-A6ED4054F9E4F86D: Ten years later, alarm fatigue is still a safety concern — https://psnet.ahrq.gov/issue/ten-years-later-alarm-fatigue-still-safety-concern

No review details supplied.
Related (useful_with): https://vedokrok.com/knowledge/route-alerts-by-urgency-not-one-undifferentiated-channel
