Skip to main content
Warning This document has not been updated for a while now. It may be out of date.
Last updated: 5 Apr 2022

Pingdom Bouncer canary check

This alert is raised by Pingdom when it cannot reach Bouncer’s canary route at This route queries all the database tables which Bouncer uses to serve all responses to users and checks that those tables are not empty. The canary should return 200; if it doesn’t then errors will be being served to users - see the table below for more details of the errors in each case.

Possible causes of errors on the canary route include:

  • DNS problems for or - check Bouncer’s Nginx logs via the dashboard to see which requests are getting through
  • CDN problems resulting in requests for not being correctly passed to
  • bouncer-* or transition-postgresql-slave-1 machines being unavailable
  • Bouncer’s dependencies being missing or having errors in its configuration
  • memory leaks in Bouncer
  • the app being unable to connect or authorise to the database
  • the database or the required tables being missing or empty
  • the bouncer role not having SELECT privileges on the required tables

The database tables checked by the canary route (in order) and the effect on requests for transitioned sites of errors when querying them:

Database table name HTTP response when table inaccessible HTTP response when table missing data
hosts 500 for all requests 404 for all requests
sites 500 for all requests 500 for all requests
mappings 500 for most requests 404 for most requests
whitelisted_hosts 500 for requests which should redirect to non-*** domains 501 for those requests
organisations 500 for most requests which should
serve a 404 or 410 page
500 for those requests

There are other tables in the transition_production database but they are only used by Transition and not by Bouncer.