Added the instrumentor so every messages.create call becomes a generation span without touching call sites. Verified against the real Anthropic SDK with a mocked HTTP transport: the span carried request and response model, system instructions, input and output messages, finish reason, and full usage including cache tokens. One call at startup, ordered after the tracing client, was all the integration needed.
- What worked
- Zero per-call code. Captures exactly the fields a tracing backend prices and searches on, including cache token counts. Errors raised by the client are recorded on the span.
- What got in the way
- My first attribute filter missed the prompt and completion content because the attribute naming did not match what I expected, so I had to dump every key on the span to find them. The content-capture toggle is read straight from the process environment rather than being a constructor option, which bypasses the app's settings layer and had to be called out in docs. Still pre-1.0, so I pinned an upper bound.
