Summary
When using microsoft-opentelemetry distro with MAF (Microsoft Agent Framework) instrumentation disabled, a chat gpt-4.1 span is still being emitted. This span should not appear when MAF instrumentation is turned off.
Repro Steps
- Use microsoft-opentelemetry distro
- Disable MAF instrumentation
- Invoke an agent
- Observe that a
chat span still shows up under the invoke_agent trace
Expected Behavior
No chat span should appear when MAF instrumentation is disabled.
Actual Behavior
A chat gpt-4.1 span (7.2s, 69 tokens) is emitted with full gen_ai attributes (input/output messages, token usage, cost, agent name/id). The span includes attributes like:
gen_ai.agent.namegen_ai.agent.idmicrosoft.gen_ai.cost.inputmicrosoft.gen_ai.cost.outputgen_ai.usage.input_tokensgen_ai.usage.output_tokensgen_ai.response.model: gpt-4.1
Screenshot
(See attached image showing the chat span with metadata appearing under invoke_agent trace even with MAF instrumentation disabled)
Environment
- Distro: microsoft-opentelemetry (Python)
- Agent Framework: MAF (Microsoft Agent Framework)
- Model: gpt-4.1
Related
Summary
When using microsoft-opentelemetry distro with MAF (Microsoft Agent Framework) instrumentation disabled, a
chat gpt-4.1span is still being emitted. This span should not appear when MAF instrumentation is turned off.Repro Steps
chatspan still shows up under theinvoke_agenttraceExpected Behavior
No chat span should appear when MAF instrumentation is disabled.
Actual Behavior
A
chat gpt-4.1span (7.2s, 69 tokens) is emitted with full gen_ai attributes (input/output messages, token usage, cost, agent name/id). The span includes attributes like:gen_ai.agent.namegen_ai.agent.idmicrosoft.gen_ai.cost.inputmicrosoft.gen_ai.cost.outputgen_ai.usage.input_tokensgen_ai.usage.output_tokensgen_ai.response.model: gpt-4.1Screenshot
(See attached image showing the chat span with metadata appearing under invoke_agent trace even with MAF instrumentation disabled)
Environment
Related