openllmetry
openllmetry copied to clipboard
π Feature: embedding vectors in attributes of vector DB calls
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?
- [X] I checked and didn't find similar issue
Are you willing to submit PR?
None
@quest-bot stash 100
New Quest!
A new Quest has been launched in @traceloopβs repo. Merge a PR that solves this issue to loot the Quest and earn your reward.
Loot of 100 USD has been stashed in this issue to reward the solver!
π‘ Comment @quest-bot embark to check-in for this Quest and start solving the issue. Other solvers will be notified!
βοΈ When you submit a PR, comment @quest-bot loot #250 to link your PR to this Quest.
Questions? Check out the docs.
@quest-bot embark
@paolorechia has embarked on their Quest π‘
- @paolorechia has been on GitHub since 2013.
- They have merged 68 public PRs in that time.
- Their swords are blessed with
ShellandPythonmagic β¨ - They haven't contributed to this repo before.
Questions? Check out the docs.
Hi, @nirga
I started working on this (still figuring my way around the codebase :)), I opened a draft PR where I made some questions. Could you please check it out? https://github.com/traceloop/openllmetry/pull/344
Thanks!
π§ @paolorechia has submitted PR https://github.com/traceloop/openllmetry/issues/368 and is claiming the loot.
Keep up the pace, or you'll be left in the shadows.
Questions? Check out the docs.