-
Notifications
You must be signed in to change notification settings - Fork 104
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
🚀 Feature: embedding vectors in attributes of vector DB calls #250
Comments
@quest-bot stash 100 |
New Quest!A new Quest has been launched in @traceloop’s repo. Loot of 100 USD has been stashed in this issue to reward the solver! 🗡 Comment ⚔️ When you submit a PR, comment Questions? Check out the docs. |
@quest-bot embark |
@paolorechia has embarked on their Quest 🗡
Questions? Check out the docs. |
🧚 @paolorechia has submitted PR #368 and is claiming the loot. Keep up the pace, or you'll be left in the shadows. Questions? Check out the docs. |
Which component is this feature for?
All Packages
🔖 Feature description
We need to extract and report embedding vectors that are sent and returned for
query
calls to vector DBs like Chroma, Weaviate, Pinecone, etc.🎤 Why is this feature needed ?
More visiblity into what's happening when calling a vector DB
✌️ How do you aim to achieve this?
This isn't straightforward - these might be large, so sending them as attributes might not make sense and we'll need to think of the proper OTEL format to use (logs? span events?)
🔄️ Additional Information
Consult on slack before working on it.
👀 Have you spent some time to check if this feature request has been raised before?
Are you willing to submit PR?
None
The text was updated successfully, but these errors were encountered: