traceloop / traceloop/openllmetry
🚀 Feature: Tracing support for Amazon Bedrock agents
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 7.4k
- Forks
- 1.1k
- Avg merge
- 8d 14h
- Merged PRs (30d)
- 2
Description
Which component is this feature for?
Bedrock Instrumentation
🔖 Feature description
Add tracing support for Amazon Bedrock agents.
🎤 Why is this feature needed ?
The response from a Bedrock agent includes a trace that details the steps being orchestrated by the agent. The trace helps us follow the agent's reasoning process that leads it to the response it gives at that point in the conversation.
✌️ How do you aim to achieve this?
- Add instrumentation logic for the
bedrock-agent-runtimeservice and patch theinvoke_agentmethod. - Create spans for each Bedrock trace event with the appropriate timestamps and attributes.
🔄️ Additional Information
No response
👀 Have you spent some time to check if this feature request has been raised before?
- I checked and didn't find similar issue
Are you willing to submit PR?
Yes I am willing to submit a PR!
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 with the Bedrock Instrumentation entry point and the bedrock-agent-runtime service's invoke_agent method. Inspect the response trace events and determine how their timestamps and attributes map to spans. Done means each Bedrock trace event is represented with the appropriate span data and the instrumentation supports agent tracing.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, python
- Domain
- cloud, observability
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100