---
id: opentelemetry-instrumentation-tornado
version: "0.65b0"
license: Apache-2.0
license_treatment: permissive
maintenance: active
---

# opentelemetry-instrumentation-tornado — Tornado instrumentation for OpenTelemetry

License: permissive · Maintenance: active · Downloads: 4.2M/mo

## What it is and what it does

This package integrates OpenTelemetry tracing into Tornado web applications by building on OpenTelemetry's WSGI instrumentation layer. It automatically captures HTTP request and response details—headers, status codes, paths, and timing—and exports them to OpenTelemetry backends for distributed tracing and observability. The package depends on opentelemetry-api, opentelemetry-instrumentation, opentelemetry-semantic-conventions, and opentelemetry-util-http to provide the core tracing infrastructure and standardized span attributes.

You install it alongside your Tornado application, and it hooks into the request lifecycle to emit trace spans without requiring code changes to your handlers. It's designed for developers building microservices or multi-service systems where you need end-to-end visibility into how requests flow through Tornado services and across service boundaries.

Use it for:

- Trace HTTP requests across a Tornado microservice to diagnose latency and failure patterns
- Export request spans to a backend like Jaeger or Zipkin for distributed tracing visualization
- Monitor Tornado application health by correlating traces with metrics and logs
- Debug request routing and middleware behavior in complex Tornado applications
- Collect standardized HTTP telemetry for compliance or performance auditing

## Worth the install?

AI-flagged interpretation of the facts above — verify before relying.

Adds OpenTelemetry tracing instrumentation to Tornado web applications, automatically capturing HTTP request and response metadata for observability.

Yes, if you are running Tornado in a microservice or multi-service environment where distributed tracing is valuable. The package is actively maintained, has no known vulnerabilities, and carries low install friction. The beta status and reliance on WSGI middleware (which may not fully align with Tornado's async model) warrant testing in your specific use case before production deployment.

## Install

pip install opentelemetry-instrumentation-tornado
uv add opentelemetry-instrumentation-tornado
poetry add opentelemetry-instrumentation-tornado

## Installing opentelemetry-instrumentation-tornado

Before you install: Low friction installation with a small, focused dependency tree. The package is actively maintained with a recent release and no known vulnerabilities, though it carries a beta status designation.

License in practice: Licensed under Apache-2.0 (permissive), allowing use in proprietary and open-source projects with minimal restrictions beyond attribution.

Quickstart:

pip install opentelemetry-instrumentation-tornado

from opentelemetry.instrumentation.tornado import TornadoInstrumentor
TornadoInstrumentor().instrument()

Requires Python 3.10 or later; Tornado application must be initialized before instrumentation is applied.

Verify before relying:

- Whether the WSGI middleware foundation fully covers Tornado's async request handling model
- Performance overhead when tracing high-volume request streams
- Compatibility with Tornado versions not explicitly listed in classifiers

## Package facts

- License: Apache-2.0 (permissive)
- Python support: supports_current
- Install friction: low
- Maintenance: active
- Downloads: 4.2M/month (top 5,000 on PyPI)
- Known vulnerabilities: none known

## Tags

tornado tracing instrumentation, opentelemetry tornado, tornado request tracing, tornado observability, tornado http monitoring, opentelemetry wsgi tornado, tornado distributed tracing, observability, tracing, tornado

[View on SkillFed](https://skillfed.io/packages/opentelemetry-instrumentation-tornado) · [View on PyPI](https://pypi.org/project/opentelemetry-instrumentation-tornado/)