open-telemetry / open-telemetry/opentelemetry-python-genai
[agno] Capture conversation ID from request arguments or instance
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 39
- Forks
- 63
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 175
Description
[!NOTE]
This issue was generated with AI assistance and requires investigation and confirmation prior to being worked on.
Part of #555.
Currently gen_ai.conversation.id is only extracted from result.session_id after execution completes. If session_id is supplied in run/arun call arguments or configured on the agent/team/workflow instance, it should be captured at span start so it is present even when execution fails before returning a result.
- Semconv mapping:
gen_ai.conversation.idoninvoke_agentandinvoke_workflow
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the instrumentation for run/arun calls and the invoke_agent and invoke_workflow spans. Check how session_id is read from call arguments and agent, team, or workflow instances, then verify that gen_ai.conversation.id is present when execution fails before returning a result.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- observability-sre
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 65/100