Skip to main content

OpenTracing support for Pyramid applications

Project description

This package enables distributed tracing in Pyramid projects via The OpenTracing Project. Once a production system contends with real concurrency or splits into many services, crucial (and formerly easy) tasks become difficult: user-facing latency optimization, root-cause analysis of backend errors, communication about distinct pieces of a now-distributed system, etc. Distributed tracing follows a request on its journey from inception to completion from mobile/browser all the way to the microservices.

As core services and libraries adopt OpenTracing, the application builder is no longer burdened with the task of adding basic tracing instrumentation to their own code. In this way, developers can build their applications with the tools they prefer and benefit from built-in tracing instrumentation. OpenTracing implementations exist for major distributed tracing systems and can be bound or swapped with a one-line configuration change.

If you want to learn more about the underlying python API, visit the python source code.

If you are migrating from the 0.x series, you may want to read the list of breaking changes.


Run the following command:

$ pip install pyramid_opentracing

Setting up Tracing for All Requests

In order to implement tracing in your system (for all the requests), add the following lines of code to your site’s Configuration section to enable the tracing tween:

# OpenTracing settings

# defaults to True
config.add_attributes({'ot.trace_all': True})

# defaults to []
# only valid if 'opentracing_trace_all' == True
config.add_attributes({'ot.traced_attributes': ['host', 'method', ...]})

# an optional module-level callable invoked after Span is created, taking
# span and request as parameters.
config.add_attributes({'ot.start_span_cb': 'my_main_module.start_span_cb'})

# One valid underlying OpenTracing implementation as
# one either ONE of these three values:

# 1. A PyramidTracing object.
config.add_attributes({'ot.tracing': PyramidTracing(my_ot_tracer)})

# 2. A module-level callable, invoked once, returning a PyramidTracing
#    and receiving the settings, such as: create_tracing(**settings).
config.add_attributes({'ot.tracing_callable', 'my_main_module.utils.create_tracing')

# 3. OR a module-level callable, invoked once, returning an opentracing
#    compliant Tracer with optional parameters.
config.add_attributes({'ot.tracer_callable', 'opentracing.Tracer'})
config.add_attributes({'ot.tracer_parameters', ...})

# enable the tween

Alternatively, you can configure the tween through an INI file:

ot.trace_all = true
ot.start_span_cb = my_main_module.start_span_cb
ot.traced_attributes = host
ot.tracing_callable = my_main_module.utils.create_tracing
pyramid.includes = pyramid_opentracing

Once the tween has been included, if ot.tracing was not directly set, a new instance will be created and will exist in registry.settings['ot.tracing'] for any further consumption.

Note: Valid request attributes to trace are listed [here]( When you trace an attribute, this means that created spans will have tags with the attribute name and the request’s value.

Tracing Individual Requests

If you don’t want to trace all requests to your site, you can use function decorators to trace individual view functions. This can be done by managing a globally unique PyramidTracing object yourself, and then adding the following lines of code to any file that has view functions:

# get_tracer() should return a globally-unique PyramidTracing object.
from my_tracing_mod import get_tracing

tracing = get_tracing()

# put the decorator after @view_config, if used
def some_view_func(request):
    ... #do some stuff

This tracing method doesn’t use the tween, so there’s no need to include that one.

The optional arguments allow for tracing of request attributes. For example, if you want to trace metadata, you could pass in @tracing.trace(‘headers’) and request.headers would be set as a tag on all spans for this view function.


Here is an tween example of a Pyramid application that uses the Pyramid tween to log all requests:

Here is an client server example of an application that acts as both a client and server, with a manually managed tracer (you will need to install the waitress module).

Other examples are included under the examples directrory.

Breaking changes from 0.x

Starting with the 1.0 version, a few changes have taken place from previous versions:

  • PyramidTracer has been renamed to PyramidTracing, although PyramidTracer can be used still as a deprecated name.

  • ot.base_tracer and ot.base_tracer_func still work, but have been deprecated.

  • When using the Tween layer, ot.trace_all defaults to True.

  • When no opentracing.Tracer is provided, PyramidTracing will rely on the global tracer.

Further Information

If you’re interested in learning more about the OpenTracing standard, please visit or join the mailing list. If you would like to implement OpenTracing in your project and need help, feel free to send us a note at

Project details

Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

pyramid_opentracing-1.0.0.tar.gz (13.4 kB view hashes)

Uploaded Source

Supported by

AWS AWS Cloud computing and Security Sponsor Datadog Datadog Monitoring Fastly Fastly CDN Google Google Download Analytics Microsoft Microsoft PSF Sponsor Pingdom Pingdom Monitoring Sentry Sentry Error logging StatusPage StatusPage Status page