Posted on October 22, 2026 by Adnan Rahic, Bindplane by Dynatrace Turn on an AI coding agent's telemetry and it throws a wall of text at you. It's expensive to store and what's worse, you can't make sense of it. It's all OpenTelemetry native, though. So you can shape it in the Collector before sending it to a telemetry backend. Which leaves one question. What do you actually need? I gave Claude Code a small task. Fix two failing tests, add a few boundary tests. With every content flag on, that one run produced 181 telemetry records and 289 KB of JSON. Every answer is a counter or a short attribute.

I don't need prompts, file bodies or diffs. If no dashboard, alert, or query reads a field, it isn't observability. It's storage you're paying to index. An agent runs a loop: Prompt, model call, tool call, result, decide, repeat. One interaction is a claude_code. interaction span with an llm_request child per model turn and a tool child per tool call. With OTEL_LOG_TOOL_CONTENT on, each tool span gets a tool. output event holding whatever the tool returned. That's a directory listing. When the tool is Read, the event is the file. A 40 KB file becomes a 40 KB span event. Logs have the same shape.

tool_result and tool_decision events carry tool_parameters, the full arguments to the tool. For a Write that's the whole file. Same content as the span event, stored twice. Metrics carry identity instead. Every data point has session. email and two account ids. Each new session created a fresh set of time series that never goes away. Twenty five sessions gave me 300 series for eight metrics. The default instrumentation is written for debugging one agent run, not for running a fleet. Tool content lands in traces and logs both. Metrics are keyed on attributes that belong on the resource, or nowhere.

None of that is wrong for a single developer watching a single session. It's wrong at 200 sessions a day. The agent won't change its defaults for you, so the pipeline has to. One OTLP receiver that'll ingest Claude Code's internal telemetry. Every signal is fanned into two pipelines, a raw one and an optimized one, each with its own exporter, all six landing in the same Grafana LGTM container. The raw pipeline is the control group. name and a batch processor. The optimized pipeline carries the processors we’ll add in this