Episode

#58 Fixing Monitoring's Bad Signal-to-Noise Ratio

Podcast
Reliability Enablers
Published
Sep 17, 2024
Duration seconds
507
Processing state
not_requested
Canonical source
https://read.srepath.com/p/58-fixing-monitorings-bad-signal
Audio
https://api.substack.com/feed/podcast/148997261/03c0386f4291fe3af1477575505b47c8.mp3
JSON
/v1/public/podcasts/reliability-enablers-6320409/episodes/58-fixing-monitoring-s-bad-signal-to-noise-ratio
Markdown
/podcast/reliability-enablers-6320409/58-fixing-monitoring-s-bad-signal-to-noise-ratio.md

Actions

  • POST https://stenobird.com/v1/public/podcasts/reliability-enablers-6320409/episodes/58-fixing-monitoring-s-bad-signal-to-noise-ratio/transcription-requests
    Idempotently request low-priority transcript generation for this episode.
  • GET https://stenobird.com/podcast/reliability-enablers-6320409/58-fixing-monitoring-s-bad-signal-to-noise-ratio.md
    Read the agent-friendly Markdown representation of this episode resource.

Summary

Monitoring in the software engineering world continues to grapple with poor signal-to-noise ratios. It’s a challenge that’s been around since the beginning of software development and will persist for years to come. The core issue is the overwhelming noise from non-essential data, which floods systems with useless alerts. This interrupts workflows, affects personal time, and even disrupts sleep. Sebastian dove into this problem, highlighting that the issue isn't just about having meaningless pages but also the struggle to find valuable information amidst the noise. When legitimate alerts get lost in a sea of irrelevant data, pinpointing the root cause becomes exceptionally hard. Sebastian proposes a fundamental fix for this data overload: be deliberate with the data you emit. When instrumenting your systems, be intentional about what data you collect and transport. Overloading with irrelevant information makes it tough to isolate critical alerts and find the one piece of data that indicates a problem. To combat this, focus on: * Being Deliberate with Data . Make sure that every piece of telemetry data serves a clear purpose and aligns with your observability goals. * Filtering Data Effectively . Improve how you filter incoming data to eliminate less relevant information and retain what's crucial. * Refining Alerts . Optimize alert rules such as creating tiered alerts to distinguish between critical issues and minor warnings. Dan Ravenstone, who leads platform at Top Hat, discussed “triaging alerts” recently. He shared that managing millions of alerts, often filled with noise, is a significant issue. His advice: scrutinize alerts for value, ensuring they meet the criteria of a good alert, and discard those that don’t impact the user journey . According to Dan, the anato…