traceloop / traceloop/openllmetry
🚀 Feature: Tracing support for Amazon Bedrock knowledge bases
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 knowledge bases.
🎤 Why is this feature needed ?
Developers may configure their RAG application to use the RetrieveAndGenerate API to query their Bedrock knowledge base and generate responses from the information it retrieves. They may also call the Retrieve API to query their knowledge base with information retrieved directly from the knowledge base.
✌️ How do you aim to achieve this?
- Add instrumentation logic for the
bedrock-agent-runtimeservice and patch theretreiveandretrieve_and_generatemethods. - Create spans for the requests.
🔄️ 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 integration, then review the Retrieve and RetrieveAndGenerate API documentation linked in the issue. Trace both methods and define spans for their requests; the work is done when both knowledge-base operations are instrumented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, python
- Domain
- observability
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100