Skip to main content
This guide will help you instrument your Django application(s) with OpenTelemetry and send traces to Checkly.

Step 1: Install the OpenTelemetry SDK

Install the relevant OpenTelemetry packages:
Terminal

Step 2: Initialize the instrumentation

Based on the web server you are using, you need to initialize the OpenTelemetry SDK and set up the necessary instrumentation.

Gunicorn

Open your gunicorn.config.py file and add the following code. This will initialize the OpenTelemetry SDK and set up the necessary instrumentation. Notice the HttpHeaderSampler class. This is a custom, head-based sampler that will only sample spans that are generated by Checkly by inspecting the trace state. This way you only pay for the egress traffic generated by Checkly and not for any other traffic. Note the code in the post_fork function. This will instrument your Django app with OpenTelemetry.
gunicorn.config.py

uWSGI

When using uWSGI, you can use the post_fork hook to instrument your Django app with OpenTelemetry. Note you will need to install the uwsgidecorators package.
Terminal
And then add the following code to your wsgi.py file.
wsgi.py

Step 3: Start your app with the instrumentation

Toggle on Import Traces and grab your OTel API key in the OTel API keys section of the Traces page in the Checkly app and take a note of the endpoint for the region you want to use. Checkly OTEL API keys Now, export your API key in your shell by setting the OTEL_EXPORTER_OTLP_HEADERS environment variable.
Next, export the endpoint for the region you want to use and give your service a name.
Then, explicitly set the protocol to use for the OTLP exporter.
We are using the standard OpenTelemetry environment variables here to configure the OTLP exporter. Finally, start your app using the relevant command: For Gunicorn, your startup command will look similar to
Terminal
For uWSGI, your startup command will look similar to
Terminal
🎉 You are done. Any interactions with your app that are triggered by a Checkly synthetic monitoring check will now generate traces, which are sent back to Checkly and displayed in the Checkly UI.