Sensory Friendly Monitoring–Keep the Noise Down
summary
Monitoring setup advice that reduces interruption cost: shows that a brief interruption causes a 25-minute recovery loss, AP-style test performance drops by 0.5 points after interruptions, and simple tasks’ error rate triples under multitasking. Recommends categorizing PagerDuty alerts (false positives/negatives, fragile or frequent), route only true emergencies as phone calls, send lower-priority events to chat/email, add redundant endpoints to survive a Slack 3-hour outage, audit EC2/AWS/Kubernetes alerts regularly, and run a recurring “sprint cleaning” to delete or automate noisy alerts.
AI-written summary · about
chapters (4)
related talks
19mSensory Friendly Monitoring: Keeping the Noise Down
19mSensory Friendly Monitoring: Keeping the Noise Down
19mSensory Friendly Monitoring
26mSensory Friendly Monitoring- Keeping the Noise Down
27mSensory Friendly Monitoring: Keeping the Noise Down
06mSensory Friendly Monitoring
21mSensory Friendly Monitoring: Keeping Noise Down
12mHow not to burn out your monitoring team