opentelemetry-instrumentation-lancedb
OpenTelemetry Lancedb instrumentation
Decision gist · record as of 2026-08-14
Yes, if you are already using OpenTelemetry and LanceDB in production. The package is actively maintained, has no known vulnerabilities, and low install friction. Install only if you have an OpenTelemetry exporter already configured; the instrumentation alone produces no output without a collector backend.AI-flagged interpretation of the facts on this page — verify before relying
Before you install
- Requires Python 3.10 or later; requires an OpenTelemetry collector or exporter to be configured separately to actually export traces.
- Low friction install with four lightweight OpenTelemetry dependencies.
- Actively maintained as of 4 days ago with recent commits and a substantial upstream repository.
License · maintenance · safety
Apache-2.0 (permissive) — Apache-2.0 permissive license allows use in most commercial and open-source projects without significant 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) · 8,215,016 downloads/mo, #1,647 on PyPI
Alternatives
Verify before relying
pip install opentelemetry-instrumentation-lancedb
from opentelemetry.instrumentation.lancedb import LanceInstrumentor
LanceInstrumentor().instrument()- Whether instrumentation works with all LanceDB versions or only specific releases.
- What trace data is captured (query parameters, latency, errors) and how detailed the semantic conventions are.
- Whether the package supports async LanceDB operations or only synchronous calls.
What it is and what it does
This package wraps the official LanceDB library to automatically emit OpenTelemetry traces for every client-side call. It integrates with the OpenTelemetry ecosystem, meaning traces are formatted according to semantic conventions and can be exported to any backend that accepts OpenTelemetry signals—Jaeger, Datadog, New Relic, or any other collector.
You install it, call `LanceInstrumentor().instrument()` once at startup, and then all subsequent LanceDB operations are traced without further code changes. It depends on opentelemetry-api, opentelemetry-instrumentation, and two semantic-conventions packages to define how database operations are represented in traces.
Use it for
- Debug slow LanceDB queries by viewing end-to-end traces in your observability backend.
- Monitor production vector database operations and correlate them with application traces.
- Troubleshoot connection issues or failures by inspecting trace spans and error attributes.
- Measure LanceDB latency distribution across your application's request lifecycle.
Worth the install?
AI-flagged interpretation of the facts on this page. Verify before relying on it.
Yes, if you are already using OpenTelemetry and LanceDB in production.
The package is actively maintained, has no known vulnerabilities, and low install friction. Install only if you have an OpenTelemetry exporter already configured; the instrumentation alone produces no output without a collector backend.
Install
opentelemetry-instrumentation-lancedb on PyPI
Before you install
Low friction install with four lightweight OpenTelemetry dependencies. Actively maintained as of 4 days ago with recent commits and a substantial upstream repository.
Requires Python 3.10 or later; requires an OpenTelemetry collector or exporter to be configured separately to actually export traces.
License in practice
Apache-2.0 permissive license allows use in most commercial and open-source projects without significant restrictions.
Quickstart
pip install opentelemetry-instrumentation-lancedb
from opentelemetry.instrumentation.lancedb import LanceInstrumentor
LanceInstrumentor().instrument()Verify before relying
- Whether instrumentation works with all LanceDB versions or only specific releases.
- What trace data is captured (query parameters, latency, errors) and how detailed the semantic conventions are.
- Whether the package supports async LanceDB operations or only synchronous 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 | 8,215,016 / month, #1,647 on PyPI 30-day window, as of 2026-08-14 |
| Known vulnerabilities | None known OSV.dev, checked 2026-08-14 |
Evidence: opentelemetry_instrumentation_lancedb-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 › “opentelemetry lancedb tracing”
- opentelemetry-instrumentation-lancedbAdds distributed tracing instrumentation for LanceDB client calls,…
- llama-index-vector-stores-lancedbIntegrates LanceDB as a vector store backend for LlamaIndex, enabling…
- opentelemetry-instrumentation-boto3sqsAdds distributed tracing to Boto3 SQS calls via OpenTelemetry,…
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-qdrant · opentelemetry-instrumentation-milvus · opentelemetry-instrumentation-chromadb · opentelemetry-instrumentation-weaviate · opentelemetry-instrumentation-pinecone · opentelemetry-instrumentation-marqo · opentelemetry-instrumentation-ollama · lancedb · lance-namespace · opentelemetry-instrumentation-boto