traceloop / traceloop/openllmetry
🚀 Feature: re-write LlamaIndex instrumentation to use LlamaIndex `CallbackManager`
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?
LlamaIndex Instrumentation
🔖 Feature description
Right now, we monkey-patch classes and methods in LlamaIndex which requires endless work and constant maintenance. LlamaIndex has a system for callbacks that can potentially be used to create/end spans without being too coupled with with the framework's inner structure.
🎤 Why is this feature needed ?
Support LlamaIndex entirely and be future-proof to internal API changes
✌️ How do you aim to achieve this?
Look into LlamaIndex callback_manager and how other frameworks are using it.
🔄️ 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?
None
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 LlamaIndex Instrumentation component and investigate LlamaIndex's callback_manager and CallbackManager documentation, then compare how other frameworks use callbacks. Done means instrumentation creates and ends spans through the callback system rather than monkey-patching LlamaIndex classes and methods, while supporting the framework more completely.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- observability
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100