News for hackers. Stuff that matters.
Re:Conflating the Roles of Alerting and Dashboards by dredmorbius on Friday March 04, 2016 @04:53PM (#11227124)
Good, though I find Rob Ewashuk's "My Philosophy on Alerting" essay (Google SRE) better:

https://docs.google.com/a/gravitant.com/document/d/199PqyG3U...

Particularly:

Pages [alerts] should be urgent, important, actionable, and real.

They should represent either ongoing or imminent problems with your service.

Err on the side of removing noisy alerts – over-monitoring is a harder problem to solve than under-monitoring.

You should almost always be able to classify the problem into one of: availability & basic functionality; latency; correctness (completeness, freshness and durability of data); and feature-specific problems.

Symptoms are a better way to capture more problems more comprehensively and robustly with less effort.

Include cause-based information in symptom-based pages or on dashboards, but avoid alerting directly on causes.

The further up your serving stack you go, the more distinct problems you catch in a single rule. But don't go so far you can't sufficiently distinguish what's going on.

If you want a quiet oncall rotation, it's imperative to have a system for dealing with things that need timely response, but are not imminently critical.

There are no comments on this comment yet.