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

# opentelemetry-instrumentation-weaviate — OpenTelemetry Weaviate instrumentation

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

## What it is and what it does

This package integrates Weaviate vector database client calls into OpenTelemetry's distributed tracing infrastructure. When installed and initialized, it automatically captures spans for operations sent to Weaviate through the official Weaviate Python client library, allowing you to observe and debug client-side behavior within your broader observability stack.

It's designed for teams already using OpenTelemetry for application tracing who need visibility into vector database interactions. The instrumentation hooks into the Weaviate client and emits traces using OpenTelemetry's semantic conventions for AI operations, integrating seamlessly with existing tracing backends (Jaeger, Datadog, etc.) without requiring changes to your Weaviate client code.

Use it for:

- Debug slow or failing Weaviate queries by correlating them with application traces in a distributed tracing backend.
- Monitor vector database latency and error rates as part of your application's observability pipeline.
- Trace end-to-end requests through a microservice architecture that includes Weaviate lookups.
- Analyze Weaviate client behavior in production without modifying application code beyond one initialization call.

## Worth the install?

AI-flagged interpretation of the facts above — verify before relying.

Adds distributed tracing to Weaviate vector database client calls using OpenTelemetry, capturing spans for observability of client-side operations.

Yes, if you are already using OpenTelemetry for application tracing and need visibility into Weaviate client operations. The package is actively maintained, has no known vulnerabilities, and integrates cleanly with standard observability infrastructure. Install it only if your observability strategy already includes OpenTelemetry; it adds no value in isolation.

## Install

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

## Installing opentelemetry-instrumentation-weaviate

Before you install: Low friction installation with a pure-Python wheel. Maintained actively with recent releases; last commit 2026-08-10. Depends on four OpenTelemetry packages (opentelemetry-api, opentelemetry-instrumentation, opentelemetry-semantic-conventions-ai, opentelemetry-semantic-conventions), all standard observability infrastructure.

License in practice: Licensed under Apache-2.0 (permissive), allowing use in proprietary and open-source projects with minimal restrictions beyond attribution.

Quickstart:

pip install opentelemetry-instrumentation-weaviate

from opentelemetry.instrumentation.weaviate import WeaviateInstrumentor

WeaviateInstrumentor().instrument()

Requires Python 3.10 or later. Assumes you have already configured an OpenTelemetry tracer provider and exporter in your application.

Verify before relying:

- Whether this instrumentation works with all Weaviate client versions or has specific compatibility constraints.
- Performance overhead of tracing on typical Weaviate query workloads.

## Package facts

- License: Apache-2.0 (permissive)
- Python support: supports_current
- Install friction: low
- Maintenance: active
- Downloads: 6.8M/month (top 5,000 on PyPI)
- Known vulnerabilities: none known

## Tags

weaviate tracing instrumentation, opentelemetry weaviate, vector db observability, distributed tracing weaviate, weaviate client spans, opentelemetry instrumentation, observability, vector-db, tracing

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