Team Guide to Software Operability

Matthew Skelton, Rob Thatcher, and Alex Moore

This is a sample of the book's content.Buy on Leanpub

Table of Contents

Team Guide to Software Operability

Team Guides for Software
Foreword
Introduction
1. What does good operability look like?
2. Core practices for good software operability
3. Use Run Book collaboration to increase operability and prevent operational issues
4. Use modern log aggregation for deep operational insights
5. Use Deployment Verification Tests and Endpoint Healthchecks for rapid feedback on environments
6. Use information radiators and dashboards to drive effective behaviour and good psychological responses
7. Make operability part of the software product
8. Appendix
- 8.1 Adapt your logging techniques to the technology characteristics
- 8.2 Understand how the complexity of modern distributed systems drives a need for a focus on operability
Terminology
References and further reading
Run Book template
About the authors
Conflux Books
Notes

Team Guide to Software Operability/1. What does good operability look like?

1. What does good operability look like?

(This chapter is not available in this edition of the book.)

Previous

Introduction

Up next

2. Core practices for good software operability

In this chapter

1. What does good operability look like?