---
id: opentelemetry-instrumentation-qdrant
version: "0.62.3"
license: Apache-2.0
license_treatment: permissive
maintenance: active
---

# opentelemetry-instrumentation-qdrant — OpenTelemetry Qdrant instrumentation

License: permissive · Maintenance: active · Downloads: 6.9M/mo

## 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 above — verify before relying.

Adds distributed tracing to Qdrant vector database client calls, capturing telemetry data for observability and debugging of vector search operations.

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

pip install opentelemetry-instrumentation-qdrant
uv add opentelemetry-instrumentation-qdrant
poetry add opentelemetry-instrumentation-qdrant

## Installing opentelemetry-instrumentation-qdrant

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.

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()

Requires Python 3.10 or later; an active OpenTelemetry SDK and exporter must be configured separately to collect and export traces.

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_current
- Install friction: low
- Maintenance: active
- Downloads: 6.9M/month (top 5,000 on PyPI)
- Known vulnerabilities: none known

## Tags

qdrant tracing instrumentation, opentelemetry vector database, distributed tracing qdrant, observability vector search, qdrant client telemetry, opentelemetry instrumentation, trace qdrant operations, observability, vector-database, tracing

[View on SkillFed](https://skillfed.io/packages/opentelemetry-instrumentation-qdrant) · [View on PyPI](https://pypi.org/project/opentelemetry-instrumentation-qdrant/)