Skip to content

Actions: microsoft/opentelemetry-distro-python

Actions

Auto-label issues by component

Actions

Loading...
Loading

Show workflow options

Create status badge

Loading
issue-auto-label.yml
20 workflow runs
20 workflow runs

Filter by Event

⌥ + click/return to exclude

Filter by Status

⌥ + click/return to exclude

Filter by Branch

⌥ + click/return to exclude

Filter by Actor

⌥ + click/return to exclude
[Bug]: Foundry Router - gen_ai.response.model is not the served model Auto-label issues by component #20: Issue #273 opened by damien-claveau-amadeus-com
21s
21s
[Bug]: Traces are dropped occassionally Auto-label issues by component #19: Issue #253 opened by TaoChenOSU
9s
9s
[Question]: Auto-label issues by component #18: Issue #231 opened by nadahaninou
11s
11s
[Bug]: LangGraph agents in Foundry Hosted agents are not emitting gen_ai.agent.* metadata Auto-label issues by component #17: Issue #225 opened by shivamMg
21s
21s
[Bug]: Documentation improvements Auto-label issues by component #16: Issue #211 opened by JimDaly
12s
12s
[Question]: Wrapt version > 2.0.0 is causing failures due to a breaking change causing the langchain spans to not be generated. Auto-label issues by component #15: Issue #208 opened by rads-1996
18s
18s
LangGraph hosted agent: gen_ai.output.messages text part content is a stringified Python list, not GenAI-spec text Auto-label issues by component #14: Issue #189 opened by ninghu
1m 10s
1m 10s
invoke_agent wrapper span omits tool-call turns and gen_ai.tool.definitions, violating GenAI semconv Auto-label issues by component #13: Issue #172 opened by ninghu
15s
15s
[Bug]: OpenAI agent chat traces don't contain input/output messages and other fields Auto-label issues by component #12: Issue #167 opened by shivamMg
48s
48s
Bug: NonRecordingSpan crashes with 'NonRecordingSpan object has no attribute context' when observability exporter is enabled Auto-label issues by component #11: Issue #166 opened by pratapladhani
28s
28s
InvokeAgent spans emit non-spec gen_ai input/output message format Auto-label issues by component #10: Issue #160 opened by ninghu
2m 2s
2m 2s
InvokeAgent spans emit non-spec gen_ai input/output message format Auto-label issues by component #9: Issue #159 opened by ninghu
2m 6s
2m 6s
[Feature]: Add proper token usage extraction for LangChain tracer to match langchain-azure's normalization Auto-label issues by component #8: Issue #158 opened by nagkumar91
2m 13s
2m 13s
Add a way to pass the agent ID to use_microsoft_opentelemetry Auto-label issues by component #7: Issue #148 opened by ninghu
30s
30s
[OpenAI Agents Auto-Instrument] Auto-instrumented spans from GenAISemanticProcessor missing all baggage attributes Auto-label issues by component #6: Issue #135 opened by fpfp100
11s
11s
[OpenAI Agents Auto-Instrument] Auto-instrumented spans have hardcoded agent identity instead of actual agent details from baggage Auto-label issues by component #5: Issue #134 opened by fpfp100
15s
15s
[OpenAI Agents Auto-Instrument] GenAISemanticProcessor maps turn and other unrecognized span data types to unknown operation name Auto-label issues by component #4: Issue #133 opened by fpfp100
15s
15s
[OpenAI Agents Auto-Instrument] GenAISemanticProcessor missing cross-span tool_call_id correlation from GenerationSpan to FunctionSpan Auto-label issues by component #3: Issue #131 opened by fpfp100
24s
24s
[OpenAI Agents Auto-Instrument] ResponseSpanData mapped to chat operation produces duplicate span names with GenerationSpanData Auto-label issues by component #2: Issue #130 opened by fpfp100
10s
10s
AgentFrameworkInstrumentor should support enable_sensitive_data via instrumentation_options Auto-label issues by component #1: Issue #124 opened by benke520
18m 56s
18m 56s