WSGI

If the WSGI web framework you’re using doesn’t have a dedicated integration, wrap your app with logfire.instrument_wsgi() to see every request it handles (the status, how long it took, and any errors) as a trace (the full journey of one request, made of nested spans, where each span is one unit of work with a name, a start, and a duration) in Logfire.

WSGI is the standard interface between synchronous Python web servers and apps. If you’re on Flask or Django, prefer their dedicated integrations (Flask, Django), which capture route details this generic wrapper can’t.

What you’ll capture

Each request as a span, with its HTTP status and duration
The request method and path
Any errors raised while handling the request

Before you start

You’ll need a Logfire project. Open Add data in your project (top navigation) and follow the setup for your language: it signs your machine in with logfire auth (a browser sign-in, no token to copy) and, for production or other languages, creates a write token (the credential your app uses to send data). New to Logfire? Start with Getting Started.

Installation

Install logfire with the wsgi extra:

Terminal

pip install 'logfire[wsgi]'

Terminal

uv add 'logfire[wsgi]'

Usage

Add two lines to your app: logfire.configure() to connect to your project, and logfire.instrument_wsgi(), which wraps your app so every request is recorded. The example below uses the standard library wsgiref server.

main.py

from wsgiref.simple_server import make_server

import logfire

logfire.configure()


def app(env, start_response):
    start_response('200 OK', [('Content-Type', 'text/html')])
    return [b'Hello World']


app = logfire.instrument_wsgi(app)

with make_server('', 8000, app) as httpd:
    # Serve until process is killed
    httpd.serve_forever()

Run it with python main.py.

Verify it worked

With the app running, open http://localhost:8000/ in your browser.

Then open your project in the Logfire web app and go to the Live view. Within a few seconds you should see a span for the request. Click it to see its duration, the method and path, and the response status.

Troubleshooting

Not seeing your requests in Logfire? Check these first:

logfire.configure() runs before logfire.instrument_wsgi(). Configure the connection first, then wrap the app.
You serve the wrapped app. instrument_wsgi() returns a new app object; make sure that’s the one your server runs.
Your write token is set. In local development, run logfire projects use <your-project>; in production, set the LOGFIRE_TOKEN environment variable. See Getting Started.
You actually sent a request. Spans appear only after the app is hit; reload the URL above.

Advanced

Passing options to the OpenTelemetry instrumentor

The keyword arguments of logfire.instrument_wsgi() are passed to the OpenTelemetryMiddleware class of the OpenTelemetry WSGI Instrumentation package.