opentelemetry-instrumentation-weaviate
OpenTelemetry Weaviate instrumentation
Decision gist · record as of 2026-08-14
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.AI-flagged interpretation of the facts on this page — verify before relying
Before you install
- Requires Python 3.10 or later.
- Assumes you have already configured an OpenTelemetry tracer provider and exporter in your application.
- Low friction installation with a pure-Python wheel.
License · maintenance · safety
Apache-2.0 (permissive) — Licensed under Apache-2.0 (permissive), allowing use in proprietary and open-source projects with minimal restrictions beyond attribution.
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,815,561 downloads/mo, #1,843 on PyPI
Alternatives
Verify before relying
pip install opentelemetry-instrumentation-weaviate
from opentelemetry.instrumentation.weaviate import WeaviateInstrumentor
WeaviateInstrumentor().instrument()- Whether this instrumentation works with all Weaviate client versions or has specific compatibility constraints.
- Performance overhead of tracing on typical Weaviate query workloads.
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 on this page. Verify before relying on it.
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
opentelemetry-instrumentation-weaviate on PyPI
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.
Requires Python 3.10 or later. Assumes you have already configured an OpenTelemetry tracer provider and exporter in your application.
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()
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 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,815,561 / month, #1,843 on PyPI 30-day window, as of 2026-08-14 |
| Known vulnerabilities | None known OSV.dev, checked 2026-08-14 |
Evidence: opentelemetry_instrumentation_weaviate-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 › “weaviate tracing instrumentation”
- opentelemetry-instrumentation-weaviateAdds distributed tracing to Weaviate vector database client calls…
- apache-airflow-providers-weaviateIntegrates Weaviate vector database operations into Apache Airflow…
- 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-chromadb · opentelemetry-instrumentation-qdrant · opentelemetry-instrumentation-milvus · opentelemetry-instrumentation-lancedb · opentelemetry-instrumentation-pinecone · opentelemetry-instrumentation-marqo · opentelemetry-instrumentation-ollama · weaviate-client · opentelemetry-instrumentation-cassandra · opentelemetry-instrumentation-sklearn