opentelemetry-instrumentation-psycopg2
OpenTelemetry psycopg2 instrumentation
Decision gist · record as of 2026-08-14
Yes, if you are already using OpenTelemetry for observability and need to trace PostgreSQL queries via psycopg2. The low installation friction, active maintenance, permissive license, and zero known vulnerabilities make it a straightforward addition to an observability stack. The beta status is typical for OpenTelemetry instrumentation packages and should not be a blocker for production use if your observability requirements are clear.AI-flagged interpretation of the facts on this page — verify before relying
Before you install
- Requires Python 3.10 or later; psycopg2 must be installed separately and an OpenTelemetry tracer provider must be configured before instrumentation will emit traces.
- Low friction installation with a pure-Python wheel and three stable OpenTelemetry runtime dependencies.
- Actively maintained as of 2026-08-13 with recent releases, though marked as beta status.
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-07-16 (29 days) · last repo commit 2026-08-13 · 1,086 stars
0 known vulnerabilities (OSV.dev, 2026-08-14) · 48,289,711 downloads/mo, #594 on PyPI
Alternatives
Verify before relying
pip install opentelemetry-instrumentation-psycopg2
from opentelemetry.instrumentation.psycopg2 import Psycopg2Instrumentor
Psycopg2Instrumentor().instrument()- Whether instrumentation works with all psycopg2 versions or has specific compatibility constraints
- Performance overhead of tracing on high-volume query workloads
- Whether automatic instrumentation covers connection pooling scenarios
What it is and what it does
This package integrates psycopg2 PostgreSQL connections with OpenTelemetry's distributed tracing framework. When installed and activated, it automatically wraps psycopg2 database operations to emit trace spans—recording SQL queries, execution time, and connection details—without requiring code changes to your application. This enables you to observe database behavior alongside application and infrastructure metrics in a unified observability platform.
The instrumentation depends on three OpenTelemetry libraries: the core API, a generic database instrumentation layer (dbapi), and the instrumentation framework itself. It targets Python 3.10 and later, and is actively maintained by the OpenTelemetry project, though still in beta. The package is distributed as a pure-Python wheel with low installation friction.
Use it for
- Trace PostgreSQL queries in microservices to identify slow database calls during distributed request flows
- Monitor connection lifecycle and query patterns in production applications using OpenTelemetry collectors
- Debug application performance by correlating database operations with application and infrastructure traces
- Collect query execution metrics and SQL statement details for compliance or performance auditing
- Integrate PostgreSQL observability into existing OpenTelemetry deployments without modifying application code
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 observability and need to trace PostgreSQL queries via psycopg2.
The low installation friction, active maintenance, permissive license, and zero known vulnerabilities make it a straightforward addition to an observability stack. The beta status is typical for OpenTelemetry instrumentation packages and should not be a blocker for production use if your observability requirements are clear.
Install
opentelemetry-instrumentation-psycopg2 on PyPI
Before you install
Low friction installation with a pure-Python wheel and three stable OpenTelemetry runtime dependencies. Actively maintained as of 2026-08-13 with recent releases, though marked as beta status.
Requires Python 3.10 or later; psycopg2 must be installed separately and an OpenTelemetry tracer provider must be configured before instrumentation will emit 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-psycopg2
from opentelemetry.instrumentation.psycopg2 import Psycopg2Instrumentor
Psycopg2Instrumentor().instrument()
Verify before relying
- Whether instrumentation works with all psycopg2 versions or has specific compatibility constraints
- Performance overhead of tracing on high-volume query workloads
- Whether automatic instrumentation covers connection pooling scenarios
Package facts
| License | Apache-2.0 permissive |
| Python support | Supports the current Python release >=3.10 |
| Install friction | Low. Pure-Python wheel |
| Runtime dependencies | 3 packagesopentelemetry-apiopentelemetry-instrumentation-dbapiopentelemetry-instrumentation |
| Maintenance | Actively maintained 29 days since the last release |
| Last repo commit | |
| First released | |
| Downloads | 48,289,711 / month, #594 on PyPI 30-day window, as of 2026-08-14 |
| Known vulnerabilities | None known OSV.dev, checked 2026-08-14 |
| Classifiers | Development Status :: 4 - BetaIntended Audience :: DevelopersLicense :: OSI Approved :: Apache Software LicenseProgramming Language :: PythonProgramming Language :: Python :: 3Programming Language :: Python :: 3.10Programming Language :: Python :: 3.11Programming Language :: Python :: 3.12Programming Language :: Python :: 3.13Programming Language :: Python :: 3.14 |
Evidence: opentelemetry_instrumentation_psycopg2-0.65b0-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 › “psycopg2 tracing”
- opentelemetry-instrumentation-psycopg2Adds distributed tracing instrumentation to psycopg2 database…
- google-cloud-sqlcommenterAutomatically injects metadata comments into SQL queries executed…
- azure-monitor-opentelemetryBundles OpenTelemetry SDK and Azure Monitor exporters to instrument…
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 google-cloud-sqlcommenter · opentelemetry-instrumentation-cassandra · opentelemetry-instrumentation-psycopg · opentelemetry-instrumentation-sqlalchemy · opentelemetry-instrumentation-tortoiseorm · opentelemetry-instrumentation-dbapi · opentelemetry-instrumentation-asyncpg · opentelemetry-instrumentation-pymssql · opentelemetry-instrumentation-pymysql · opentelemetry-instrumentation-sqlite3