Observability on Board — switch on the OpenTelemetry your tools already ship

Your tools already speak OpenTelemetry.

Claude Code, Docker, Keycloak and others already come with observability on board. Each of the episodes below shows you how to switch on the telemetry the tool ships already.

Ship telemetry toUse an OTLP endpoint you already have, from another vendor or your platform team. This one needs a one-time setup step: save your endpoint and the episodes fill it in.Set your endpointRun an OpenTelemetry Collector on your machine and watch telemetry arrive in its terminal. No account needed.More detailsShip straight to Bronto. You need an account and an API key with ingest permission.More details

Pick one and every episode adapts: Bronto, a local Collector, or any OTLP endpoint you already use.

Episodes

Watch the series on YouTube

EP 01
Claude Code
Tokens, cost, tool decisions and every LLM request, exported with one settings file.
tracesmetricslogs
EP 02
Docker Buildx
Span names are your Dockerfile steps, and one span name tells you exactly where your cache breaks.
tracesmetrics
EP 03
Keycloak
One login is 28 spans, and the database is 0.7% of it. The trace shows where the other 99% goes.
tracesmetricslogs
EP 04
OpenTofu
26 seconds of resource work inside a 10-second apply, and the trace names the resources that set the floor.
traces
EP 05
eve
Every model call reads ~7,000 tokens and writes ~200, a 30:1 ratio on every step of every turn.
traces
NEXT EPISODE
Your tool?
Know a tool with observability on board that we haven't covered? Tell us which one and where its OpenTelemetry docs live.
Request an episode

Your tools already speak OpenTelemetry.

Episodes

Claude Code

Docker Buildx

Keycloak

OpenTofu

eve

Your tool?