OpenLabs handbook

OpenTelemetry Visual Handbook

Watch the telemetry move, then read the bytes that moved.

Every concept as a model you can take apart: the service graph on top, the OTLP payload underneath, and the same running state producing both.

Roadmap

The order in which the concepts hold each other up. Not a queue — later phases reach back, and the map shows it.

Your progress0 of 18
  • done
  • where you are
  • not written yet
  • The Wire · reference, not a step
  1. 01 The Problem Why three signals with no thread between them leave you blind.
  2. 02 The Model Trace, metric, log: the shape each one has before any vendor touches it.
  3. 03 The Architecture SDK, Collector, backend — and what each one is allowed to change.
  4. 04 Instrumentation Getting the signal out of code you wrote and code you did not.
  5. 05 Operating at Scale Sampling, backpressure, and the rollout that does not page anyone.

Articles and labs

Each phase pairs prose with a model. The article says what is true; the lab is the thing running, and you can break it.

01 The Problem

Why three signals with no thread between them leave you blind.

Articles

Labs

02 The Model

Trace, metric, log: the shape each one has before any vendor touches it.

Articles

Labs

03 The Architecture

SDK, Collector, backend — and what each one is allowed to change.

Articles

Labs

04 Instrumentation

Getting the signal out of code you wrote and code you did not.

Articles

  • Instrumenting what you did not write coming
  • A library depends on the API only coming
  • Context does not cross a queue by itself coming

Labs

05 Operating at Scale

Sampling, backpressure, and the rollout that does not page anyone.

Articles

Labs

Handbook assessment

The cumulative assessment has not been authored yet. Available labs and articles remain open for study.