Book
Practical Monitoring
Mike Julian
Summary
Mike Julian teaches the principles behind monitoring rather than any specific tool, working chapter by chapter through common anti-patterns first, then the design patterns that replace them. From there it covers alerting and on-call rotation design, a short primer on the statistics monitoring depends on, and then the layers a real system needs watched, business metrics, frontend, application, server, network, and security. The vendor-neutral approach means the lessons transfer even after the specific monitoring stack changes, which the book treats as inevitable.
Target Readers
- Engineers building a monitoring strategy for the first time who need principles before picking a specific tool
- On-call teams drowning in alert noise who need the anti-pattern diagnosis before adding more dashboards
- Teams that monitor infrastructure metrics well but have never systematically covered frontend or business-level monitoring
Tags
Colophon
- Publisher
- オライリー・ジャパン
- ISBN
- 978-4873118642
- Published
- Jan 2019
- List price
- ¥3,080incl. taxMay differ from the actual selling price on Amazon
Get this book
* The link above is an advertisement via Amazon Associates.Related Books
Next Books
- Recommended
Observability Engineering
Charity Majors, Liz Fong-Jones, George Miranda
Reason: After designing 'watch predefined metrics' monitoring with Julian's 'Practical Monitoring', advance to observability, which lets you explore even unknown failures. Majors et al.'s 'Observability Engineering' explains systems where high-cardinality events let you ask 'why did it happen?' after the fact, going beyond the limits of monitoring.
- Related
Site Reliability Engineering
Betsy Beyer, Chris Jones, Jennifer Petoff, Niall Richard Murphy
Reason: After designing 'what to measure' with 'Practical Monitoring', advance to the philosophy of tying those metrics to organizational decisions. Google's 'Site Reliability Engineering' elevates monitoring data—via SLIs/SLOs/error budgets—into criteria for 'when to halt feature work and invest in reliability'.
- Related
Release It!, 2nd Edition
Design and Deploy Production-Ready Software
Michael T. Nygard
Reason: After setting up failure detection with 'Practical Monitoring', advance to designing how the system itself absorbs the detected failures. The stability patterns in Nygard's 'Release It!'—circuit breakers, timeouts—become an implementation toolkit for automatically containing the failures monitoring surfaces.