Skip to content

Tracing is resulting in orphaned traces #4285

@josephp27

Description

@josephp27

Hi, no matter what I try, I cannot get the traces to not create orphaned traces. I currently have a multi-agent system where there is a supervisor that has tools and subagents (that also have tools).

Agent Trace ID Expected
supervisor 0xb32dfdde... ✅ Root
agent1 0x4e64db01... ❌ Should have parent and same trace as supervisor
agent2 0x0bfd5184... ❌ Should have parent and same trace as supervisor
agent3 0x3c85fadd... ❌ Should have parent and same trace as supervisor

What's interesting is that the separate trace ids i look into will show tool executions properly. it seems to only be happening on the first layer from supervisor -> subagents/tools as far as i can tell

Tried on ADK Version 1.23.0 AND 1.16.0

This seems similar to this one that's happening in go: google/adk-go#439

Thanks!

Metadata

Metadata

Assignees

No one assigned

    Labels

    tracing[Component] This issue is related to OpenTelemetry tracing

    Type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions