uptrace
OpenTelemetry Python distribution for Uptrace
Decision gist · record as of 2026-08-14
Yes, if you are already using Uptrace or planning to adopt it for observability. The package reduces boilerplate compared to configuring OpenTelemetry directly, and it has active maintenance, no known vulnerabilities, and permissive licensing. Install it as part of your observability stack setup, not as a standalone tool—it requires an Uptrace account to be useful.AI-flagged interpretation of the facts on this page — verify before relying
Before you install
- Requires Python 3.9 or later; also requires an Uptrace account and DSN to export data.
- Low friction installation with a pure Python wheel.
- Active maintenance with recent commits and a stable production release status.
License · maintenance · safety
BSD-3-Clause (permissive) — BSD-3-Clause is permissive; you can use this package in commercial and proprietary projects with minimal restrictions.
last release 2026-04-16 (120 days) · last repo commit 2026-08-09 · 28 stars
0 known vulnerabilities (OSV.dev, 2026-08-14) · 150,483 downloads/mo, #10,963 on PyPI
Alternatives
Verify before relying
pip install uptrace
import uptrace
from opentelemetry import trace
uptrace.configure_opentelemetry(dsn="https://...@api.uptrace.dev/...")
tracer = trace.get_tracer(__name__)- Whether the package supports automatic instrumentation for specific frameworks beyond Django, Flask, and FastAPI.
- Performance overhead of the wrapper layer compared to direct OpenTelemetry usage.
- Whether metrics and logs export are fully featured or have limitations compared to traces.
What it is and what it does
Uptrace is a Python package that simplifies integration with the Uptrace observability platform by wrapping OpenTelemetry. It handles the export of distributed traces, metrics, and logs from your Python application to Uptrace's backend, eliminating the need to manually configure OpenTelemetry exporters. The package depends on four core OpenTelemetry libraries: opentelemetry-api, opentelemetry-sdk, opentelemetry-instrumentation, and opentelemetry-exporter-otlp.
You use it by installing the package, configuring it with your Uptrace DSN, and then instrumenting your application code or frameworks. The wrapper abstracts away OpenTelemetry configuration details, making it faster to get observability running. It includes guides for popular frameworks like Django, Flask, FastAPI, and SQLAlchemy, so you can instrument web applications and database calls with minimal setup.
Use it for
- Instrument a Django or Flask web application to collect distributed traces and send them to Uptrace for performance analysis.
- Export application metrics and logs alongside traces to correlate performance issues with error patterns.
- Monitor database queries in SQLAlchemy-based applications by collecting query spans and latency data.
- Set up observability for a FastAPI microservice without manually configuring each OpenTelemetry component.
- Collect end-to-end traces across multiple services to debug latency and failures in distributed systems.
Worth the install?
AI-flagged interpretation of the facts on this page. Verify before relying on it.
Yes, if you are already using Uptrace or planning to adopt it for observability.
The package reduces boilerplate compared to configuring OpenTelemetry directly, and it has active maintenance, no known vulnerabilities, and permissive licensing. Install it as part of your observability stack setup, not as a standalone tool—it requires an Uptrace account to be useful.
Install
uptrace on PyPI
Before you install
Low friction installation with a pure Python wheel. Active maintenance with recent commits and a stable production release status.
Requires Python 3.9 or later; also requires an Uptrace account and DSN to export data.
License in practice
BSD-3-Clause is permissive; you can use this package in commercial and proprietary projects with minimal restrictions.
Quickstart
pip install uptrace
import uptrace
from opentelemetry import trace
uptrace.configure_opentelemetry(dsn="https://...@api.uptrace.dev/...")
tracer = trace.get_tracer(__name__)
Verify before relying
- Whether the package supports automatic instrumentation for specific frameworks beyond Django, Flask, and FastAPI.
- Performance overhead of the wrapper layer compared to direct OpenTelemetry usage.
- Whether metrics and logs export are fully featured or have limitations compared to traces.
Package facts
| License | BSD-3-Clause permissive |
| Python support | Supports the current Python release >=3.9 |
| Install friction | Low. Pure-Python wheel |
| Runtime dependencies | 4 packagesopentelemetry-apiopentelemetry-exporter-otlpopentelemetry-instrumentationopentelemetry-sdk |
| Maintenance | Actively maintained 120 days since the last release |
| Last repo commit | |
| First released | |
| Downloads | 150,483 / month, #10,963 on PyPI 30-day window, as of 2026-08-14 |
| Known vulnerabilities | None known OSV.dev, checked 2026-08-14 |
| Classifiers | Development Status :: 5 - Production/StableIntended Audience :: DevelopersLicense :: OSI Approved :: BSD LicenseProgramming Language :: PythonProgramming Language :: Python :: 3Programming Language :: Python :: 3.9Typing :: Typed |
Evidence: uptrace-1.41.0-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 uptrace exporter”
- uptraceUptrace is a thin wrapper over OpenTelemetry that exports traces,…
- opentelemetry-exporter-otlp-proto-grpcExports telemetry data from Python applications to an OpenTelemetry…
- opentelemetry-exporter-otlp-proto-httpExports OpenTelemetry observability data to an 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-logging · coralogix-opentelemetry · splunk-opentelemetry · opentelemetry-instrumentation-celery · opentelemetry-instrumentation-structlog · opentelemetry-instrumentation-django · opentelemetry-exporter-prometheus-remote-write · opentelemetry-instrumentation-requests