I. Introduction
by Jennifer Petoff, Niall Richard Murphy, Chris Jones, Betsy Beyer
Site Reliability Engineering
- Foreword
- Preface
- I. Introduction
- 1. Introduction
- 2. The Production Environment at Google, from the Viewpoint of an SRE
- II. Principles
- 3. Embracing Risk
- 4. Service Level Objectives
- 5. Eliminating Toil
- 6. Monitoring Distributed Systems
- Definitions
- Why Monitor?
- Setting Reasonable Expectations for Monitoring
- Symptoms Versus Causes
- Black-Box Versus White-Box
- The Four Golden Signals
- Worrying About Your Tail (or, Instrumentation and Performance)
- Choosing an Appropriate Resolution for Measurements
- As Simple as Possible, No Simpler
- Tying These Principles Together
- Monitoring for the Long Term
- Conclusion
- 7. The Evolution of Automation at Google
- 8. Release Engineering
- 9. Simplicity
- III. Practices
- 10. Practical Alerting from Time-Series Data
- 11. Being On-Call
- 12. Effective Troubleshooting
- 13. Emergency Response
- 14. Managing Incidents
- 15. Postmortem Culture: Learning from Failure
- 16. Tracking Outages
- 17. Testing for Reliability
- 18. Software Engineering in SRE
- 19. Load Balancing at the Frontend
- 20. Load Balancing in the Datacenter
- 21. Handling Overload
- 22. Addressing Cascading Failures
- 23. Managing Critical State: Distributed Consensus for Reliability
- 24. Distributed Periodic Scheduling with Cron
- 25. Data Processing Pipelines
- Origin of the Pipeline Design Pattern
- Initial Effect of Big Data on the Simple Pipeline Pattern
- Challenges with the Periodic Pipeline Pattern
- Trouble Caused By Uneven Work Distribution
- Drawbacks of Periodic Pipelines in Distributed Environments
- Introduction to Google Workflow
- Stages of Execution in Workflow
- Ensuring Business Continuity
- Summary and Concluding Remarks
- 26. Data Integrity: What You Read Is What You Wrote
- 27. Reliable Product Launches at Scale
- IV. Management
- 28. Accelerating SREs to On-Call and Beyond
- 29. Dealing with Interrupts
- 30. Embedding an SRE to Recover from Operational Overload
- 31. Communication and Collaboration in SRE
- 32. The Evolving SRE Engagement Model
- V. Conclusions
- 33. Lessons Learned from Other Industries
- 34. Conclusion
- A. Availability Table
- B. A Collection of Best Practices for Production Services
- C. Example Incident State Document
- D. Example Postmortem
- E. Launch Coordination Checklist
- F. Example Production Meeting Minutes
- Bibliography
- Index
Part I. Introduction
This section provides some high-level guidance on what SRE is and why it is different from more conventional IT industry practices.
Ben Treynor Sloss, the senior VP overseeing technical operations at Google—and the originator of the term “Site Reliability Engineering”—provides his view on what SRE means, how it works, and how it compares to other ways of doing things in the industry, in Chapter 1.
We provide a guide to the production environment at Google in Chapter 2 as a way to help acquaint you with the wealth of new terms and systems you are about to meet in the rest of the book.
-
No Comment
..................Content has been hidden....................
You can't read the all page of ebook, please click here login for view all page.