My Philosophy on Alerting

Lobsters·11 points·calvin·about 9 years ago·docs.google.com

My Philosophy on Alerting based my observations while I was a Site Reliability Engineer at Google Author: Rob Ewaschuk <[email protected]> Introduction Vernacular Monitor for your users Cause-based alerts are bad…

Read the full article at docs.google.com →

#philosophy #alerting #devops #practices #based #observations #engineer #reliability

Related stories

Questioning "Best Practices" for Software Development: Practices are Contextual, Never Best (2011)ambysoft.com
Lobsters · 2 points · over 7 years ago
Knightmare: A DevOps Cautionary Taledougseven.com
Lobsters · 15 points · over 11 years ago
mir: A lightweight JIT compiler based on MIR (Medium Internal Representation) and C11 JIT compiler and interpreter based on MIRgithub.com
Lobsters · 10 points · about 3 years ago
The Death of the Traditional Software Engineer? Meet the Forward Deployed Engineer (FDE)dev.to
DEV Community · 7 points · about 15 hours ago
A look into NASA's coding philosophytechinasia.com
Lobsters · 8 points · about 9 years ago
A Letter to a Junior Engineerbuilttoadapt.io
Lobsters · 7 points · over 8 years ago

Related topics

practices121 programming301 pdf131 art57 complexity8 computer79 terminal58 coaching3 software198 metaphor3 original12 life80