Error logging

Errors are automatically logged to the database with stack traces. Each error is associated with the current user and tenant.

Tenant admins see only their tenant’s errors
Platform admins see all errors

View them at /admin/logs in the admin panel, filterable by 4xx/5xx and searchable.

The ErrorLog model

class ErrorLog(Model):
    error_type    # NotFoundError, ValidationError, etc.
    message       # error message
    path          # request path
    method        # HTTP method
    user_id       # user who triggered it, if authenticated
    tenant_id     # tenant scope
    stack_trace   # full traceback, for 500 errors
    created_at    # when it occurred

Pair this with request tracking. The request ID in your application logs matches the request that produced the error record, so you can move between the two.

Failed background jobs write here too. With JOB_ENABLE_MONITORING=true the record also carries memory, CPU and thread counts from the moment of failure.

⌘I

Get started

Building the UI

Backend

Features

Tooling

Testing

Deployment

The ErrorLog model

​The ErrorLog model

The ErrorLog model