opentelemetry-instrumentation-qdrant
OpenTelemetry Qdrant instrumentation
Decision gist · record as of 2026-08-14
Yes, if you already use OpenTelemetry for observability and need visibility into Qdrant operations. The low install friction, active maintenance, permissive license, and zero known vulnerabilities make it a safe addition. Install only if you have an OpenTelemetry SDK and exporter configured; the instrumentation alone produces no output.AI-flagged interpretation of the facts on this page — verify before relying
Before you install
- Requires Python 3.10 or later; an active OpenTelemetry SDK and exporter must be configured separately to collect and export traces.
- Low friction install with a small, well-maintained dependency tree.
- The package is actively maintained with a recent release and depends only on core OpenTelemetry libraries.
License · maintenance · safety
Apache-2.0 (permissive) — Apache-2.0 permissive license allows free use, modification, and distribution in both open-source and commercial projects with minimal restrictions.
last release 2026-08-10 (4 days) · last repo commit 2026-08-10 · 7,377 stars
0 known vulnerabilities (OSV.dev, 2026-08-14) · 6,879,902 downloads/mo, #1,823 on PyPI
Alternatives
Verify before relying
pip install opentelemetry-instrumentation-qdrant
from opentelemetry.instrumentation.qdrant import QdrantInstrumentor
QdrantInstrumentor().instrument()- Whether instrumentation works with all Qdrant client library versions or only specific versions.
- What trace data fields are captured and whether they include vector operation details.
- Whether the package supports async Qdrant client calls.
What it is and what it does
This package is an OpenTelemetry instrumentation plugin that automatically captures distributed traces from the official Qdrant client library. When installed and activated, it intercepts client-side calls to Qdrant and exports trace data (spans) to your configured OpenTelemetry backend, enabling visibility into vector database operations for debugging, performance analysis, and system monitoring.
The package integrates into the OpenTelemetry ecosystem and requires that you have an OpenTelemetry SDK and exporter already configured in your application. It adds no tracing logic itself—it only bridges Qdrant calls into the tracing infrastructure you've already set up. This makes it a lightweight addition to applications that already use OpenTelemetry for observability.
Use it for
- Debug slow or failing vector search queries by examining trace spans and timing data.
- Monitor Qdrant operations in production to detect performance regressions or bottlenecks.
- Correlate Qdrant database calls with upstream application traces for end-to-end request visibility.
- Collect metrics on vector database usage patterns and operation frequencies across services.
- Troubleshoot integration issues between your application and Qdrant in distributed systems.
Worth the install?
AI-flagged interpretation of the facts on this page. Verify before relying on it.
Yes, if you already use OpenTelemetry for observability and need visibility into Qdrant operations.
The low install friction, active maintenance, permissive license, and zero known vulnerabilities make it a safe addition. Install only if you have an OpenTelemetry SDK and exporter configured; the instrumentation alone produces no output.
Install
opentelemetry-instrumentation-qdrant on PyPI
Before you install
Low friction install with a small, well-maintained dependency tree. The package is actively maintained with a recent release and depends only on core OpenTelemetry libraries.
Requires Python 3.10 or later; an active OpenTelemetry SDK and exporter must be configured separately to collect and export traces.
License in practice
Apache-2.0 permissive license allows free use, modification, and distribution in both open-source and commercial projects with minimal restrictions.
Quickstart
pip install opentelemetry-instrumentation-qdrant
from opentelemetry.instrumentation.qdrant import QdrantInstrumentor
QdrantInstrumentor().instrument()Verify before relying
- Whether instrumentation works with all Qdrant client library versions or only specific versions.
- What trace data fields are captured and whether they include vector operation details.
- Whether the package supports async Qdrant client calls.
Package facts
| License | Apache-2.0 permissive |
| Python support | Supports the current Python release <4,>=3.10 |
| Install friction | Low. Pure-Python wheel |
| Runtime dependencies | 4 packagesopentelemetry-apiopentelemetry-instrumentationopentelemetry-semantic-conventions-aiopentelemetry-semantic-conventions |
| Maintenance | Actively maintained 4 days since the last release |
| Last repo commit | |
| First released | |
| Downloads | 6,879,902 / month, #1,823 on PyPI 30-day window, as of 2026-08-14 |
| Known vulnerabilities | None known OSV.dev, checked 2026-08-14 |
Evidence: opentelemetry_instrumentation_qdrant-0.62.3-py3-none-any.whl
Tags
Let your AI agent find packages like this
Example. Real query, live index.
You found this page by searching. An agent finds it by wishing: SkillFed indexes 14,416 PyPI packages by what they can do, searchable in plain language.
wish › “qdrant tracing instrumentation”
- opentelemetry-instrumentation-qdrantAdds distributed tracing to Qdrant vector database client calls,…
- openlitOpenLIT provides OpenTelemetry-native auto-instrumentation for…
- opentelemetry-instrumentation-pymemcacheAdds OpenTelemetry tracing instrumentation to pymemcache client…
Give your agent the search over MCP, or paste the wish link into any chat.
More Monitoring packages
Wraps any iterable to display a real-time progress bar in the terminal or Jupyter notebook, showing iteration count, elapsed time, and estimated time remaining.
Provides generated Python code for OpenTelemetry semantic conventions, enabling standardized attribute naming and constant definitions for instrumentation and telemetry collection.
Install it if you are using OpenTelemetry and want to follow semantic conventions correctly.
Provides the reference implementation of the OpenTelemetry API for collecting and exporting traces, metrics, and logs from Python applications.
Provides the abstract API and interfaces for OpenTelemetry instrumentation in Python, defining how to emit traces, metrics, and logs without tying code to a specific SDK implementation.
Exports OpenTelemetry observability data to an OpenTelemetry Collector using Protobuf-encoded messages over HTTP.
Install it if you are using OpenTelemetry in Python and need to send data to a Collector over HTTP.
Provides automatic instrumentation commands and programmatic APIs to inject distributed tracing into Python applications without code changes, detecting and instrumenting packages used by your program.
Install it if you need distributed tracing without code changes and have compatible instrumented packages in your environment.
See also opentelemetry-instrumentation-lancedb · opentelemetry-instrumentation-marqo · opentelemetry-instrumentation-milvus · opentelemetry-instrumentation-weaviate · opentelemetry-instrumentation-chromadb · qdrant-client · opentelemetry-instrumentation-pinecone · nucliadb-telemetry · opentelemetry-instrumentation-llamaindex · aiobotocore-otel