Welcome to Cloud Observability in Action, your hands-on guide to applying observability in the context of cloud native environments.
Observability is the capability to continuously generate and discover actionable insights based on signals from the system under observation with the goal to influence the system.
In this book you will learn about the basic signal types (logs, metrics, traces, profiles), telemetry including agents, back-end and front-end destinations, and goood practices around dashboarding, alerting, and SLOs/SLIs.
The first five chapters of the book are now available via the Manning MEAP Program and you can find all the code snippets we use for the hands-on exercises throughout the book via the site you're on, currently.
The WIP table of contents looks as follows:
In the context of this book we focus on cloud native environments such as Kubernetes and serverless offerings (such as FaaS like AWS Lambda). We mainly use open source observability tooling (Grafana, Prometheus, Jaeger) so that you can try out everything without license costs. While it is important that we use open source tooling to show the concepts in action, they are universally applicable (that is, using any of the commerical offerings). In this chapter we have a look at an end-to-end example and define terminology, from sources to agents to destinations.
- What is Observability?
- Roles and Goals
- Example Microservices App
- Challenges and How Observability Helps
In this chapter we review different signal types most often used, how to instrument and collect each, and discuss the costs and benefits of doing that. With observability you want to take an Return-On-Investment (ROI) driven approach. In other words, you need to understand the costs of each signal type and what it enables you to do.
- Reference Example
- Assessing Instrumentation Costs
- Logs
- Metrics
- Traces
- Selecting Signals
This chapter covers signal sources. We discuss the type of sources that exist and when to select which source, how you can gain actionable insights from selecting the right sources for a task and how to deal with code you own including supply chain aspects.
- Selecting Sources
- Compute-related Sources
- Storage-related Sources
- Network-related Sources
- Your Code
In this chapter we discuss instrumentation and review different agents, from log routers to OpenTelemetry. You will learn how to select and use agents with an emphasis on what OpenTelemetry brings to the table for unified telemetry, including correlation of signals.
- Log Routers
- Metrics Collection
- OpenTelemetry
- Other Agents
- Selecting An Agent
The chapter focuses on back-ends as the source of truth for your telemetry signals. You will learn to use and select back-ends for logs, metrics, and traces with deep dives on TSDBs and column-oriented datastores such as ClickHouse.
- Back-end Destinations Terminology
- Back-end Destinations for Logs
- Back-end Destinations for Metrics
- Back-end Destinations for Traces
- Columnar Datastores
- Selecting Back-End Destinations
In the chapter we talk about front-ends as the place where you consume the telemetry signals. You will learn about pure front-ends and all-in-ones and how to go about selecting them.
- Front-ends (Grafana, Kibana/OpenSearch Dashboards)
- All-in-ones (Jaeger, Pixie, commerical offerings)
- Selecting Front-ends and All-in-ones
ETA: 12/2022
ETA: 01/2023
ETA: 01/2023
ETA: 02/2023