What is the goal of this project? To provide a clear, concise, and unbiased overview of cloud-native observability.
Why is that important? Despite untold millions of marketing dollars spent in and around observability (or maybe because of the untold millions of marketing dollars spent), cloud-native observability practice today is often inefficient, ineffective, or both. It doesn't need to be that way.
Who is this for? Observability and DevOps practitioners, SREs, end-users of observability systems, and anyone involved in building and running cloud-native software at scale.
How can you help? You can contribute in several ways --
- Adding your stories and learnings to the "Real World Examples" directory
- Helping refine and shape this repository through contributions
- Tackling a good first issue
- Giving us a star and sharing the repository!
You can also view the project milestones.
Currently, we would appreciate feedback (either via issues or pull requests) in the following areas:
- Overall structure and flow of the document.
- Overall comprehension of the text/themes.
- Un-defined, under-defined, or over-defined themes/concepts/terms.
- General feedback on the ideas.
- Illustrations and explanatory diagrams.
- README
- Foreword
- Introduction
- End-users and Engineers, Transactions and Resources
- The Anatomy of Observability
- Telemetry Creation and OpenTelemetry
- Effective Monitoring
- Effective Investigation
- Effective SLOs
- Telemetry ROI -- The Elephant in the Room
- Organizational Concerns
- Glossary
We gladly accept pull requests! Please see CONTRIBUTING.md for more.
This guide is made possible thanks to salary-paying by Lightstep.
We'd love for you to check out our report on how OpenTelemetry drives the future of observability as a companion to this whitepaper.
This work is licensed under a Creative Commons Attribution-ShareAlike 4.0 International License.
