Repository navigation
[OTel] Three different AnyValue decoders, two of them lossy #173
Description
We decode OTel AnyValue in three places and only one does it right. extraction.py silently drops array/kvlist/bytes values, loader/otlp.py JSON-dumps the raw proto structure, and only otlp_processing.py decodes it properly (and only for log bodies).
Concrete symptom: gen_ai.response.finish_reasons shows up as the literal blob {"values":[{"stringValue":"stop"}]} via one path and vanishes via another. One shared decoder fixes all three call sites.
Reacted by Liammm
Activity
Leroyyyyyyyyy commentedon Aug 16, 2026
Hi @krisztianfekete — I'd like to take this one, if it's still available.
Planning to have a PR up (with tests) in the next few days.
krisztianfekete commentedon Aug 17, 2026
Hey, sounds good, looking forward to it!
fix(otel): share one AnyValue decoder across all OTLP paths
fix(otel): narrow spec-string attributes once at the decode boundary
fix(otel): decode containers on an opt-in allowlist instead of a deny…
fix(otel): share one AnyValue decoder across all OTLP paths (agenteva…