- Apply observability in cloud native systems
- Understand observability signals, including their costs and benefits
- Apply good practices around instrumentation and signal collection
- Deliver dashboarding, alerting, and SLOs/SLIs at scale
- Choose the correct signal types for given roles or tasks
- Pick the right observability tool for any given function
- Communicate the benefits of observability to management
A well-designed observability system provides insight into bugs and performance issues in cloud native applications. They help your development team understand the impact of code changes, measure optimizations, and track user experience. Best of all, observability can even automate your error handling so that machine users apply their own fixes--no more 3AM calls for emergency outages. Purchase of the print book includes a free eBook in PDF, Kindle, and ePub formats from Manning Publications. About the technology Cloud native systems are made up of hundreds of moving parts. When something goes wrong, it's not enough to know there is a problem--you need to know where it is, what it is, and how to fix it. This book takes you beyond traditional monitoring, explaining observability systems that turn application telemetry into actionable insights. About the book Cloud Observability in Action gives you the background and techniques you need to successfully introduce observability into cloud-based serverless and Kubernetes environments. In it, you'll learn to use open standards and tools like OpenTelemetry, Prometheus, and Grafana to build your own observability system and end reliance on proprietary software. You'll discover insights from different telemetry signals, including logs, metrics, traces, and profiles. Plus, the book's rigorous cost-benefit analysis ensures you're getting a real return on your observability investment. What's inside
- Observability in and of cloud native systems
- Dashboarding, alerting, and SLOs/SLIs at scale
- Signal types for any role or task
- State-of-the-art open source observability tools
About the reader For application developers, platform owners, DevOps, and SREs. About the author Michael Hausenblas is a Product Owner in the AWS open source observability team. Table of Contents 1 End-to-end observability
2 Signal types
3 Sources
4 Agents and instrumentation
5 Backend destinations
6 Frontend destinations
7 Cloud operations
8 Distributed tracing
9 Developer observability
10 Service level objectives
11 Signal correlation