Skip to main content

OpenTracing support for Django applications

Project description

This package enables distributed tracing in Django 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.

Installation

> Currently, only Django version 1.x is supported. Pull requests are welcome for Django 2.x support.

Run the following command:

$ pip install django_opentracing

Setting up Tracing

In order to implement tracing in your system, add the following lines of code to your site’s settings.py file:

import django_opentracing

# OpenTracing settings

# if not included, defaults to False
# has to come before OPENTRACING_TRACER setting because python...
OPENTRACING_TRACE_ALL = False

# defaults to []
# only valid if OPENTRACING_TRACE_ALL == True
OPENTRACING_TRACED_ATTRIBUTES = ['arg1', 'arg2']

# Callable that returns an `opentracing.Tracer` implementation.
OPENTRACING_TRACER_CALLABLE = 'opentracing.Tracer'

# Parameters for the callable (Depending on the tracer implementation chosen)
OPENTRACING_TRACER_PARAMETERS = {
    'example-parameter-host': 'collector',
}

If you want to directly override the DjangoTracer used, you can use the following. This may cause import loops (See #10)

# some_opentracing_tracer can be any valid OpenTracing tracer implementation
OPENTRACING_TRACER = django_opentracing.DjangoTracer(some_opentracing_tracer)

Note: Valid request attributes to trace are listed [here](https://docs.djangoproject.com/en/1.9/ref/request-response/#django.http.HttpRequest). When you trace an attribute, this means that created spans will have tags with the attribute name and the request’s value.

Tracing All Requests

In order to trace all requests, set OPENTRACING_TRACE_ALL = True. If you want to trace any attributes for all requests, then add them to OPENTRACING_TRACED_ATTRIBUTES. For example, if you wanted to trace the path and method, then set OPENTRACING_TRACED_ATTRIBUTES = [‘path’, ‘method’].

Tracing all requests uses the middleware django_opentracing.OpenTracingMiddleware, so add this to your settings.py file’s MIDDLEWARE_CLASSES at the top of the stack.

MIDDLEWARE_CLASSES = [
    'django_opentracing.OpenTracingMiddleware',
    ... # other middleware classes
]

Tracing Individual Requests

If you don’t want to trace all requests to your site, then you can use function decorators to trace individual view functions. This can be done by adding the following lines of code to views.py (or any other file that has url handler functions):

from django.conf import settings

tracer = settings.OPENTRACING_TRACER

@tracer.trace(optional_args)
def some_view_func(request):
    ... # do some stuff

This tracing method doesn’t use middleware, so there’s no need to add it to your settings.py file.

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

Note: If you turn on OPENTRACING_TRACE_ALL, this decorator will be ignored, including any traced request attributes.

Accessing Spans Manually

In order to access the span for a request, we’ve provided an method DjangoTracer.get_span(request) that returns the span for the request, if it is exists and is not finished. This can be used to log important events to the span, set tags, or create child spans to trace non-RPC events.

Tracing an RPC

If you want to make an RPC and continue an existing trace, you can inject the current span into the RPC. For example, if making an http request, the following code will continue your trace across the wire:

@tracer.trace()
def some_view_func(request):
    new_request = some_http_request
    current_span = tracer.get_span(request)
    text_carrier = {}
    opentracing_tracer.inject(span, opentracing.Format.TEXT_MAP, text_carrier)
    for k, v in text_carrier.items():
        request.add_header(k,v)
    ... # make request

Example

Here is an example of a Django application that acts as both a client and server, with integrated OpenTracing tracers.

Further Information

If you’re interested in learning more about the OpenTracing standard, please visit opentracing.io 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 community@opentracing.io.

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

django_opentracing-0.1.20.tar.gz (22.9 kB view details)

Uploaded Source

Built Distributions

django_opentracing-0.1.20-py3-none-any.whl (8.7 kB view details)

Uploaded Python 3

django_opentracing-0.1.20-py2-none-any.whl (8.7 kB view details)

Uploaded Python 2

File details

Details for the file django_opentracing-0.1.20.tar.gz.

File metadata

  • Download URL: django_opentracing-0.1.20.tar.gz
  • Upload date:
  • Size: 22.9 kB
  • Tags: Source
  • Uploaded using Trusted Publishing? No
  • Uploaded via: twine/1.12.1 pkginfo/1.4.2 requests/2.20.0 setuptools/40.5.0 requests-toolbelt/0.8.0 tqdm/4.28.1 CPython/2.7.14

File hashes

Hashes for django_opentracing-0.1.20.tar.gz
Algorithm Hash digest
SHA256 4bbac6e7e019b18410ce9459185aa3180a3ea1c3db8527286b8e2e8c2d508633
MD5 a30391507c1f2a82c9c8de9e1136281e
BLAKE2b-256 9f019145133af7d059c81dfed5b4f702a42805850d17e3b003b30e413d184870

See more details on using hashes here.

File details

Details for the file django_opentracing-0.1.20-py3-none-any.whl.

File metadata

  • Download URL: django_opentracing-0.1.20-py3-none-any.whl
  • Upload date:
  • Size: 8.7 kB
  • Tags: Python 3
  • Uploaded using Trusted Publishing? No
  • Uploaded via: twine/1.12.1 pkginfo/1.4.2 requests/2.20.0 setuptools/40.5.0 requests-toolbelt/0.8.0 tqdm/4.28.1 CPython/3.4.6

File hashes

Hashes for django_opentracing-0.1.20-py3-none-any.whl
Algorithm Hash digest
SHA256 26afd31193bf124db4eb461a4653fc6e1f9fccd7618c9d9111a0e7282f9c505e
MD5 36eb1bde4a48a046579ccd2d40f9e202
BLAKE2b-256 f6904c855ef7b93bab4af8f6b66324801fa12378b28c8953a27c159a5dca9827

See more details on using hashes here.

File details

Details for the file django_opentracing-0.1.20-py2-none-any.whl.

File metadata

  • Download URL: django_opentracing-0.1.20-py2-none-any.whl
  • Upload date:
  • Size: 8.7 kB
  • Tags: Python 2
  • Uploaded using Trusted Publishing? No
  • Uploaded via: twine/1.12.1 pkginfo/1.4.2 requests/2.20.0 setuptools/40.5.0 requests-toolbelt/0.8.0 tqdm/4.28.1 CPython/2.7.14

File hashes

Hashes for django_opentracing-0.1.20-py2-none-any.whl
Algorithm Hash digest
SHA256 d870da5b6049be6528b5a0106b6c71485033c52e7d780f7a994adda15161f788
MD5 a85e955f46874973c2cfc466c6b377a1
BLAKE2b-256 760aab73713ef844774bdb6806bc71c853e72dcbb5d5a3196c6c4c514287a22f

See more details on using hashes here.

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