[agno] Capture conversation ID from request arguments or instance
Maintainers usually reply within 1 day
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 65/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- python
- Domain
- observability-sre
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.
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
- Dominant language
- Python
- Stars
- 46
- Forks
- 93
- Avg merge
- 2d 20h
- Merged PRs (30d)
- 121
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing 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.
More from open-telemetry/opentelemetry-python-genai
-
Support disabling OpenAI Agents native trace export through an environment variablePossibly taken @123liuziming claimed this 5 days ago. Openenhancement
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
open-telemetry/opentelemetry-python-genai#922 · 3 comments ·
Maintainers usually reply within 1 day
-
fix(smolagents): accept tuple inputs for messages, content, and task imagesPossibly taken @SAMurai-16 claimed this 8 days ago. Open
Difficulty 1/5 Under an hour Newbie friendliness 82/100
open-telemetry/opentelemetry-python-genai#905 ·
Maintainers usually reply within 1 day
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
open-telemetry/opentelemetry-python-genai#857 · 1 comment · 1 reaction ·
Maintainers usually reply within 1 day
-
[genai-bedrock] invoke_model body passed as a file-like object: no request parameters or input messages are recordedPossibly taken @SyedTashfin claimed this 15 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
open-telemetry/opentelemetry-python-genai#848 ·
Maintainers usually reply within 1 day
-
[genai-portkey] With content capture enabled, generator/iterator message content is consumed and sent emptyPossibly taken @SAMurai-16 claimed this 22 days ago. Openbug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
open-telemetry/opentelemetry-python-genai#829 ·
Maintainers usually reply within 1 day
All issues in open-telemetry/opentelemetry-python-genai
Similar issues
-
intake mcp-intake needs-ac needs-human-review priority:medium
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
Ikalus1988/MisakaNet#3848 · 2 comments ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 75/100
521xueweihan/HelloGitHub#4105 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
igormcsouza/bookloud#54 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
aws-samples/sample-per-model-bedrock#526 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
ok-oldking/ok-wuthering-waves#1802 ·
Maintainers usually reply within 2 days