traceAI-qdrant
OpenTelemetry instrumentation for Qdrant vector database.
Installation
pip install traceAI-qdrant
Quick Start
from fi_instrumentation import register
from traceai_qdrant import QdrantInstrumentor
from qdrant_client import QdrantClient
from qdrant_client.models import VectorParams, Distance, PointStruct
trace_provider = register(project_name="my-rag-app")
QdrantInstrumentor().instrument(tracer_provider=trace_provider)
client = QdrantClient(":memory:")
client.create_collection("documents", vectors_config=VectorParams(size=384, distance=Distance.COSINE))
client.upsert("documents", points=[
PointStruct(id=1, vector=[0.1]*384, payload={"text": "Hello"}),
PointStruct(id=2, vector=[0.2]*384, payload={"text": "World"}),
])
results = client.search("documents", query_vector=[0.15]*384, limit=5)
Instrumented Operations
| Operation | Span Name | Description |
|---|---|---|
search |
qdrant search |
Vector similarity search |
upsert |
qdrant upsert |
Insert or update points |
delete |
qdrant delete |
Delete points |
retrieve |
qdrant retrieve |
Get points by ID |
scroll |
qdrant scroll |
Iterate through points |
recommend |
qdrant recommend |
Recommendation search |
count |
qdrant count |
Count points |
License
Apache License 2.0
Metadata
Release files for traceAI-qdrant 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| traceai_qdrant-0.1.0.tar.gz | 3.4 kB | Without provenance | Details for traceai_qdrant-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| traceai_qdrant-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for traceai_qdrant-0.1.0-py3-none-any.whl |
Total release size: 8.2 kB
Release files / traceai_qdrant-0.1.0.tar.gz
| Download URL | traceai_qdrant-0.1.0.tar.gz |
|---|---|
| Size | 3.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ca5cc4625405b1bb2c47bf997088317c449787970d795f4a68f069462c88cc01
|
|
BLAKE2b-256 checksum How to use checksums |
5ab412ce560235e2884fef0edc5d56d0a17ac3e2eccb1e6ec6a6a4ba373d0c70
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.9.21 {"installer":{"name":"uv","version":"0.9.21","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"macOS","version":null,"id":null,"libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Release files / traceai_qdrant-0.1.0-py3-none-any.whl
| Download URL | traceai_qdrant-0.1.0-py3-none-any.whl |
|---|---|
| Size | 4.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
d4589f4f49c3c5e7b6e3053777d51a1e01088203e2ba4e8ab0fc1ec0168cb5a5
|
|
BLAKE2b-256 checksum How to use checksums |
c6e15f56862d32a4c5f07c3a19c893946758bef3e2248b423e56f6ff8b1584f0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.9.21 {"installer":{"name":"uv","version":"0.9.21","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"macOS","version":null,"id":null,"libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Security for traceAI-qdrant 0.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.