Technical3 min read
Technical dimension
Building observability that holds up in production. Signals, OpenTelemetry, pipelines, backends, SLOs, AI and integrity.
A doctor does not order every possible test for every patient. They pick the ones that help reach a diagnosis, without bankrupting the hospital. The technical dimension looks for the same thing for an IT system: how to get, at the right cost, the signal that lets you understand an outage.
Every chapter starts from a concrete operations problem and gives the full configuration, tested in a lab, a small environment you start on your own machine. The Labs page says which ones are published.
If you are new to the topic, start with the first three chapters of the table, in order: they set out the vocabulary used everywhere else.
Published and upcoming chapters
Section titled “Published and upcoming chapters”| Chapter | What you learn to do | Status |
|---|---|---|
| Observability in 10 minutes | tell monitoring from observability, understand metrics, logs, traces, profiles and events, link them, reason about cardinality | published, for beginners; cardinality simulator |
| OpenTelemetry end to end | follow a trace step (a span) from the application to storage, instrument, configure a minimal Collector, apply the standard’s naming conventions | published, for beginners |
| SLOs and alerting | set service quality targets (SLIs and SLOs), compute the tolerated margin of error (the error budget), alert when it melts too fast (the burn rate) instead of on thresholds | published, for beginners; error budget simulator |
| Cardinality explained | understand how a label with unlimited values multiplies series and storage, find the culprit, fix it and cap it | published, with a video and the cardinality-cost-lab |
| Who is growing the metrics bill? | find the metrics and labels that push the bill up, in three questions, then keep a monthly ranking shared with finance | published |
| Entities, Profiles, Injector | understand three OpenTelemetry pieces and their maturity: entity model, profiles signal, agent injection | published, in the OpenTelemetry section |
| OpenTelemetry and reversibility | tell data portability from operational reversibility, measure a time to exit | published, in the OpenTelemetry section |
| Collection pipelines | design a Collector: filtering, transformation, sampling, routing | planned |
| Backends and storage | choose between Prometheus, VictoriaMetrics, Elastic, Loki, Tempo, ClickHouse | planned |
| AI observability | observe inference, RAG and MCP tools with an open source stack | published, with a full course |
| Log integrity | build an audit log a third party can verify | published |
| HPC and GPU infrastructure | tie every GPU metric to a job and an account, catch silent degradation | reference architecture, course in preparation |
| Agents, RAG and MCP | per-component measurement grids, probabilistic quality SLOs | GenAI method |
| VictoriaMetrics | a metrics backend for high-cardinality workloads | course |
| Edge and IoT | observe constrained, intermittent and heterogeneous fleets | planned |
Hands-on
Section titled “Hands-on”To see these ideas move rather than read about them, try the trace explorer, the clickable architecture, the animated Collector pipeline, tail sampling or the quality SLO simulator. The rest are gathered on the tools and diagrams pages.