opentelemetry-instrumentation-jinja2
OpenTelemetry jinja2 instrumentation
Decision gist · record as of 2026-08-14
Yes, if you are already using OpenTelemetry in your application and render Jinja2 templates. It adds observability with minimal overhead and no code changes to your templates. Not necessary if you are not using OpenTelemetry or do not use Jinja2. Beta status (0.65b0) means it is stable enough for production but may see API changes.AI-flagged interpretation of the facts on this page — verify before relying
Before you install
- Requires Python 3.10 or later; requires an active OpenTelemetry tracer/exporter configured in your application.
- Low install friction with three lightweight runtime dependencies.
- Actively maintained as of 2026-08-14 with recent releases; part of the OpenTelemetry Python contrib ecosystem.
License · maintenance · safety
Apache-2.0 (permissive) — Apache-2.0 permissive license allows use in commercial and open-source projects with minimal restrictions.
last release 2026-07-16 (29 days) · last repo commit 2026-08-14 · 1,086 stars
0 known vulnerabilities (OSV.dev, 2026-08-14) · 5,043,568 downloads/mo, #2,176 on PyPI
Alternatives
Verify before relying
pip install opentelemetry-instrumentation-jinja2
from opentelemetry.instrumentation.jinja2 import Jinja2Instrumentor
from jinja2 import Environment
Jinja2Instrumentor().instrument()
env = Environment()
template = env.from_string('Hello {{ name }}')
template.render(name='World')- Whether instrumentation works with Jinja2 versions prior to the package's first release in 2020
- Performance overhead of instrumentation on high-volume template rendering
- Compatibility with async Jinja2 environments
What it is and what it does
This package integrates Jinja2 template rendering into OpenTelemetry's distributed tracing system. It automatically instruments Jinja2 environments to emit spans and metrics whenever templates are compiled or rendered, allowing you to observe template performance and behavior as part of your broader application telemetry. The instrumentation captures template names, rendering duration, and other execution details.
It is designed for applications already using OpenTelemetry for observability—it acts as a bridge between Jinja2 and your existing tracing infrastructure. The package depends on opentelemetry-api, opentelemetry-instrumentation, and wrapt to hook into Jinja2's execution without modifying your template code.
Use it for
- Monitor template rendering latency in web applications to identify performance bottlenecks in view generation.
- Correlate template execution with upstream and downstream service calls in distributed tracing dashboards.
- Debug template-related errors by examining spans and context propagation across your observability platform.
- Measure template compilation and rendering costs in high-throughput applications serving many concurrent requests.
- Audit which templates are executed and how often in production environments for compliance or optimization.
Worth the install?
AI-flagged interpretation of the facts on this page. Verify before relying on it.
Yes, if you are already using OpenTelemetry in your application and render Jinja2 templates.
It adds observability with minimal overhead and no code changes to your templates. Not necessary if you are not using OpenTelemetry or do not use Jinja2. Beta status (0.65b0) means it is stable enough for production but may see API changes.
Install
opentelemetry-instrumentation-jinja2 on PyPI
Before you install
Low install friction with three lightweight runtime dependencies. Actively maintained as of 2026-08-14 with recent releases; part of the OpenTelemetry Python contrib ecosystem.
Requires Python 3.10 or later; requires an active OpenTelemetry tracer/exporter configured in your application.
License in practice
Apache-2.0 permissive license allows use in commercial and open-source projects with minimal restrictions.
Quickstart
pip install opentelemetry-instrumentation-jinja2
from opentelemetry.instrumentation.jinja2 import Jinja2Instrumentor
from jinja2 import Environment
Jinja2Instrumentor().instrument()
env = Environment()
template = env.from_string('Hello {{ name }}')
template.render(name='World')Verify before relying
- Whether instrumentation works with Jinja2 versions prior to the package's first release in 2020
- Performance overhead of instrumentation on high-volume template rendering
- Compatibility with async Jinja2 environments
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-instrumentationwrapt |
| Maintenance | Actively maintained 29 days since the last release |
| Last repo commit | |
| First released | |
| Downloads | 5,043,568 / month, #2,176 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_jinja2-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 › “jinja2 tracing instrumentation”
- opentelemetry-instrumentation-jinja2Adds OpenTelemetry tracing instrumentation to Jinja2 template…
- opentelemetry-instrumentation-pymemcacheAdds OpenTelemetry tracing instrumentation to pymemcache client…
- opentelemetry-instrumentation-pymysqlAdds OpenTelemetry tracing instrumentation to PyMySQL database…
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-celery · opentelemetry-instrumentation-pymongo · opentelemetry-instrumentation-pyramid · coralogix-opentelemetry · opentelemetry-contrib-instrumentations · aiohttp-jinja2 · opentelemetry-instrumentation-pymemcache · opentelemetry-instrumentation-tornado · opentelemetry-instrumentation-psycopg2 · elastic-opentelemetry