You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Same gen_ai.response.id emitted across multiple spans/services, inflating token and cost accounting in Application Insights. Usage dashboards and cost assertions require manual de-dup logic; raw queries overcount by ~2x.
Workaround is to designate responsesapi as canonical source
The change uses ContextVar-based ownership so the outer agent span stops duplicating gen_ai.response.id and token-usage telemetry that already belongs to the inner chat span, while still preserving agent-level response telemetry for agents that do not rely on a chat client.
Activity
eavanvalkenburg commentedon Mar 13, 2026
I have a fix up in PR
#4685:The change uses ContextVar-based ownership so the outer agent span stops duplicating
gen_ai.response.idand token-usage telemetry that already belongs to the inner chat span, while still preserving agent-level response telemetry for agents that do not rely on a chat client.