4 ms·
Yeah I agree. Rob Ewaschuk at google has an excellent document called something like "my philosophy on monitoring". It's fresh in my mind because I've been usin
by CraigJPerry 12y ago
Yeah I agree. Rob Ewaschuk at google has an excellent document called something like "my philosophy on monitoring". It's fresh in my mind because I've been using it as a kind of social proof for improvements I've been making in the monitoring of our application.
Symptom vs cause based monitoring he calls it and I find the terminology works really well.
He doesn't mention what you allude to - this approach works very nicely alongside teams who's development practices see them iterate on features.
- henrik_w 12y agoI guess this is the document you mean: https://docs.google.com/document/d/199PqyG3UsyXlwieHaqbGiWVa8eMWi8zzAn0YfcApr8Q/edit https://docs.google.com/document/d/199PqyG3UsyXlwieHaqbGiWVa...
- nlh 12y agoShameless plug for something I've written recently on the same topic: I spent a few months researching a "philosophy" on monitoring and alerting in production environments and wrote up some (related but different) conclusions: https://www.scalyr.com/community/guides/zen-and-the-art-of-system-monitoring https://www.scalyr.com/community/guides/zen-and-the-art-of-s... https://www.scalyr.com/community/guides/how-to-set-alerts https://www.scalyr.com/community/guides/how-to-set-alerts My focus was more on system-level monitoring/alerting vs application-level, but the philosophies are similar.