Backend framework

    Django Monitoring

    Uptime, Celery health, and 500-rate monitoring for Django sites.

    What typically breaks on Django

    • ALLOWED_HOSTS misconfig after custom domain switch (DisallowedHost)
    • Celery worker idle while tasks pile up in Redis
    • Static files 404 because collectstatic skipped in CI

    What Lemwatch checks on every Django site

    HTTP uptime

    1-minute checks from multiple regions. We catch Django-specific 5xx errors, not just connection timeouts.

    Response time + Core Web Vitals

    TTFB, LCP, CLS, INP tracked over time. Alerts fire when the rolling baseline degrades, not just on hard outages.

    Content integrity

    We diff your homepage HTML and key routes. Catch silent deploys that strip critical content or break routing.

    SSL + DNS drift

    Cert expiry warnings 30 days out. DNS hash watch alerts when A/CNAME/MX records change unexpectedly.

    Works with where you deploy Django

    Lemwatch monitors the public surface, so it doesn't care which host you use. Common Django hosting stacks we see in the wild:

    Render
    Heroku
    Railway
    self-hosted gunicorn

    How we detect Django

    When you add a site, Lemwatch fingerprints the stack from the public response — in Django's case, by looking for csrfmiddlewaretoken hidden input and sessionid cookie. Detection is non-invasive and runs on every health check, so a stack migration surfaces in your changelog within 24 hours.

    Django monitoring — FAQs

    No. Lemwatch is fully black-box — it monitors what every visitor sees. No code access, no plugin install, no SDK. Add your domain and checks start within a minute.

    Other frameworks we monitor

    Start monitoring your Django site in 60 seconds

    Free plan. No credit card. No code changes.

    Get started — free