opentelemetry-instrumentation-wsgi
WSGI Middleware for OpenTelemetry
Decision gist · record as of 2026-08-14
Yes, if you are using a WSGI framework and need distributed tracing. The package is actively maintained, has no known vulnerabilities, low install friction, and permissive licensing. The beta status is typical for OpenTelemetry instrumentation libraries. Install it when you are ready to integrate your WSGI application into an observability pipeline.AI-flagged interpretation of the facts on this page — verify before relying
Before you install
- Requires Python 3.10 or later; also requires a configured OpenTelemetry tracer provider to be active in your application.
- Low install friction with a pure-Python wheel distribution.
- Actively maintained as of 2026-07-16 with recent activity; part of the OpenTelemetry ecosystem which has broad community support.
License · maintenance · safety
Apache-2.0 (permissive) — Licensed under Apache-2.0 (permissive), allowing use in commercial and proprietary projects with minimal restrictions beyond attribution.
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,603,783 downloads/mo, #589 on PyPI
Alternatives
Verify before relying
pip install opentelemetry-instrumentation-wsgi
from opentelemetry.instrumentation.wsgi import OpenTelemetryMiddleware
app = OpenTelemetryMiddleware(your_wsgi_app)- Whether the middleware automatically captures request/response headers and body content, or only timing metadata.
- Performance overhead of the instrumentation under high request volume.
- Compatibility with async WSGI frameworks or whether it is synchronous-only.
What it is and what it does
This package is a WSGI middleware component for the OpenTelemetry observability framework. It sits between your web application and the WSGI server, intercepting requests and responses to generate distributed tracing spans that record request timing and metadata. It works with any WSGI-compatible framework—Django, Flask, or others—without requiring framework-specific code changes.
The middleware integrates with OpenTelemetry's core instrumentation and semantic conventions libraries to emit spans that can be exported to tracing backends (Jaeger, Zipkin, etc.). It is currently in beta status and requires Python 3.10 or later. Installation is straightforward via pip, and it has low dependency friction with only four runtime dependencies, all from the OpenTelemetry project itself.
Use it for
- Add distributed tracing to a Flask or Django application to track request latency across microservices.
- Instrument a WSGI application to export request spans to a tracing backend for debugging production issues.
- Monitor request timing and correlate logs with traces in a multi-service deployment.
- Collect observability data from legacy WSGI frameworks 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 using a WSGI framework and need distributed tracing.
The package is actively maintained, has no known vulnerabilities, low install friction, and permissive licensing. The beta status is typical for OpenTelemetry instrumentation libraries. Install it when you are ready to integrate your WSGI application into an observability pipeline.
Install
opentelemetry-instrumentation-wsgi on PyPI
Before you install
Low install friction with a pure-Python wheel distribution. Actively maintained as of 2026-07-16 with recent activity; part of the OpenTelemetry ecosystem which has broad community support.
Requires Python 3.10 or later; also requires a configured OpenTelemetry tracer provider to be active in your application.
License in practice
Licensed under Apache-2.0 (permissive), allowing use in commercial and proprietary projects with minimal restrictions beyond attribution.
Quickstart
pip install opentelemetry-instrumentation-wsgi
from opentelemetry.instrumentation.wsgi import OpenTelemetryMiddleware
app = OpenTelemetryMiddleware(your_wsgi_app)Verify before relying
- Whether the middleware automatically captures request/response headers and body content, or only timing metadata.
- Performance overhead of the instrumentation under high request volume.
- Compatibility with async WSGI frameworks or whether it is synchronous-only.
Package facts
| License | Apache-2.0 permissive |
| Python support | Supports the current Python release >=3.10 |
| Install friction | Low. Pure-Python wheel |
| Runtime dependencies | 4 packagesopentelemetry-apiopentelemetry-instrumentationopentelemetry-semantic-conventionsopentelemetry-util-http |
| Maintenance | Actively maintained 29 days since the last release |
| Last repo commit | |
| First released | |
| Downloads | 48,603,783 / month, #589 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_wsgi-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 › “wsgi middleware tracing”
- opentelemetry-instrumentation-wsgiProvides WSGI middleware for OpenTelemetry that automatically…
- opentelemetry-util-httpProvides ASGI and WSGI middleware and HTTP utilities for…
- opentelemetry-instrumentation-flaskAdds distributed tracing to Flask web applications by instrumenting…
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-asgi · opentelemetry-instrumentation-flask · instana · opentelemetry-util-http · opentelemetry-instrumentation-django · opentelemetry-instrumentation-tornado · opentelemetry-instrumentation-pyramid · elastic-apm · opentelemetry-instrumentation-fastapi · opentelemetry-instrumentation-sklearn