Operations Anti-Patterns, DevOps Solutions

Intro

Operations Anti-patterns, DevOps Solutions

Copyright

dedication

contents

front matter

preface

acknowledgments

about this book

Who should read this book

How this book is organized: A roadmap

About the code

liveBook discussion forum

about the author

about the cover illustration

1 The DevOps ingredients

1.1 What is DevOps?

1.1.1 A little DevOps history

1.1.2 What DevOps is not

1.2 CAMS, the pillars of DevOps

1.3 Another DevOps book?

Summary

2 The paternalist syndrome

2.1 Creating barriers instead of safeguards.

2.2 Introducing the gatekeepers

2.3 Examining the gatekeepers

2.4 Curing paternalism through automation

2.5 Capturing the purpose of the approval

2.6 Structuring code for automation

2.6.1 Approval process

2.6.2 Automating approvals

2.6.3 Logging process

2.6.4 Notification process

2.6.5 Error handling

2.7 Ensuring continuous improvement

Summary

3 Operational blindness

3.1 War stories

3.2 Changing the scope of development and operations

3.3 Understanding the product

3.4 Creating operational visibility

3.4.1 Creating custom metrics.

3.4.2 Deciding what to measure

3.4.3 Defining healthy metrics

3.4.4 Failure mode and effects analysis

3.5 Making logging useful

3.5.1 Log aggregation

3.5.2 What should I be logging?

3.5.3 The hurdles of log aggregation

Summary

4 Data instead of information

4.1 Start with the user, not the data

4.2 Widgets, the dashboard building blocks

4.2.1 The line graph

4.2.2 The bar graph

4.2.3 The gauge

4.3 Giving context to your widgets

4.3.1 Giving context through color

4.3.2 Giving context through threshold lines.

4.3.3 Giving context through time comparisons

4.4 Organizing your dashboard

4.4.1 Working with dashboard rows

4.4.2 Leading the reader

4.5 Naming your dashboards

Summary

5 Quality as a condiment

5.1 The testing pyramid

5.2 Testing structure

5.2.1 Unit tests

5.2.2 Integration tests

5.2.3 End-to-end tests

5.3 Confidence in your test suite

5.3.1 Restoring confidence in your test suite

5.3.2 Avoiding vanity metrics

5.4 Continuous deployment vs. continuous delivery

5.5 Feature flags

5.6 Executing pipelines

5.7 Managing the testing infrastructure.

5.8 DevSecOps

Summary

6 Alert fatigue

6.1 War story

6.2 The purpose of on-call rotation

6.3 Defining on-call rotations

6.3.1 Time to acknowledge

6.3.2 Time to begin

6.3.3 Time to resolve

6.4 Defining alert criteria

6.4.1 Thresholds

6.4.2 Noisy alerts

6.5 Staffing on-call rotations

6.6 Compensating for being on call

6.6.1 Monetary compensation

6.6.2 Time off

6.6.3 Increased work-from-home flexibility

6.7 Tracking on-call happiness

6.7.1 Who is being alerted?

6.7.2 What level of urgency is the alert?

6.7.3 How is the alert being delivered?