🚀 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?

• I checked and didn't find similar issue

Are you willing to submit PR?

None

Start by consulting the project Slack as requested, then review how query calls to Chroma, Weaviate, and Pinecone are instrumented. Determine with maintainers whether embeddings belong in attributes, logs, or span events, and what size and representation limits apply. Done means an agreed OpenTelemetry approach and coverage for vectors sent and returned by the supported vector database calls.