# open-telemetry/opentelemetry-python-contrib

OpenTelemetry instrumentation for Python modules

Repository: https://github.com/open-telemetry/opentelemetry-python-contrib
Canonical: https://ross.abutalabs.com/products/opentelemetry-python-contrib
Homepage: https://opentelemetry.io
Language: Python
License: Apache-2.0
License Family: permissive
Last push: 2026-09-02T13:50:40+00:00

## Health v2 (maintenance only)
Score: 99/100 (v2, computed 2026-09-03T02:20:16.233290+00:00)
- activity 100, release rhythm 98, longevity 100
- inputs: {"age_days": 2490, "days_push": 0, "days_rel": 13, "gap_med": 8, "n_releases_24m": 54}
- flags: none
- formula: round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10)

## Adoption (not part of the score)
Stars 1091, forks 1049 (observed 2026-09-03T02:15:15.722415+00:00)

## What it is
A collection of OpenTelemetry instrumentation libraries for Python, providing automatic and manual instrumentation for popular Python frameworks, libraries, and modules. It emits vendor-neutral traces, metrics, and logs that can be exported to any observability backend.

## Use cases
- instrument a Flask or Django app with distributed tracing
- auto-instrument Python microservices without changing code
- export traces and metrics to Jaeger or Prometheus from Python
- trace database and HTTP client calls in a Python application
- add observability to a Python web service with zero vendor lock-in
- correlate logs and traces across Python services

## When to choose
- you need OpenTelemetry instrumentation for specific Python libraries and frameworks
- you want vendor-neutral telemetry exportable to any observability backend
- you want zero-code or automatic instrumentation for Python services

## When to avoid
- you need a full observability backend with storage and visualization - OpenTelemetry only generates and exports data
- your stack is not Python - use the OpenTelemetry contrib packages for your language instead
- you only need simple application logging without tracing or metrics

## Facets
- artifact type: library
- maturity: active
- function: tracing, monitoring, logging, middleware, sdk
- domain: monitoring, developer-tools, microservices
- platform: python, cross-platform, cloud
- tags: opentelemetry, instrumentation, telemetry, distributed-tracing, apm, observability, metrics, auto-instrumentation, devops, web-server

## Member repositories
- open-telemetry/opentelemetry-python-contrib (main) score 99

## Provenance
- Observed fields: from GitHub, fetched 2026-09-03T02:15:15.722415+00:00.
- Health v2: computed from the inputs above; adoption is never an input.
- Inferred fields (summary, facets, guidance): AI-extracted, prompt v1, taxonomy v1, on 2026-08-30T06:49:19.150801+00:00, confidence not recorded.
  - readme: https://github.com/open-telemetry/opentelemetry-python-contrib (fetched 2026-09-03T02:15:15.722415+00:00, sha a094d1cf7a7c)
  - homepage: https://opentelemetry.io (fetched 2026-08-29T12:51:57.727939+00:00, sha 51756d27c4f1)
  - site_page: https://opentelemetry.io/docs (fetched 2026-08-29T12:51:57.737764+00:00, sha 06566227bba9)
  - site_page: https://opentelemetry.io/docs/what-is-opentelemetry (fetched 2026-08-29T12:51:57.739685+00:00, sha dd58475f7d30)
  - site_page: https://opentelemetry.io/docs/demo (fetched 2026-08-29T12:51:57.742001+00:00, sha 03a34a004b8f)
  - site_page: https://opentelemetry.io/docs/concepts/signals/traces (fetched 2026-08-29T12:51:57.743944+00:00, sha 123b7f8bc630)
  - site_page: https://opentelemetry.io/docs/concepts/signals/metrics (fetched 2026-08-29T12:51:57.746010+00:00, sha 5fe9fc342c92)
  - site_page: https://opentelemetry.io/docs/concepts/signals/logs (fetched 2026-08-29T12:51:57.748201+00:00, sha 126e1fa6c0a2)
  - site_page: https://opentelemetry.io/docs/concepts/signals/baggage (fetched 2026-08-29T12:51:57.750212+00:00, sha fc18d0d07d4b)
  - site_page: https://opentelemetry.io/docs/concepts/instrumentation/zero-code (fetched 2026-08-29T12:51:57.751970+00:00, sha c811260b8c51)
- Data as of 2026-08-30T08:39:29.467469+00:00.