Bug: the trace information will be split, with both the parent and child agents having independent trace IDs when the root agent invokes the child agent.

Open
#549 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
68/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Tech stack
python
Domain
observability

Research direction

Start in in_memory_exporter.py and inspect the on_start method, especially its call to attach. Reproduce a root agent invoking a child agent and compare the collected trace IDs before and after the child starts. Done means the parent and child spans remain in the same trace rather than producing two independent trace IDs.

Written by the indexing model from the issue text.

Description

当我设置一个父智能体作为根智能体，调用子智能体时发现收集到的trace是两条独立的traceid，以ai工具分析是 in_memory_exporter.py中的on_start方法中调用attach方法会直接将当前的span置空，导致进入子智能体时被对待成了新的span。

Dominant language
Python
Stars
344
Forks
98
Avg merge
8h 17m
Merged PRs (30d)
152

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from volcengine/veadk-python

All issues in volcengine/veadk-python

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.