Sentry is a realtime event logging and aggregation platform. It specializes in monitoring errors and extracting all the information needed to do a proper post-mortem without any of the hassle of the standard user feedback loop. (From PyPI)
Typically you will be registering in response to an invite to join an organisation. In this case, you will get an email from Sentry with text such as
You have been invited to join the ORGNAME organization on Sentry.
ORGNAME is using Sentry to capture exceptions in real-time.
To accept this invitation, proceed to the following url:
When you follow the link in the email, you will be able to create an account if you do not already have one.
Documentation for Sentry is available within Sentry itself at http://judoon.tardis.ed.ac.uk/docs/.
Sentry is a very pluggable system, and as such there are multitudes of plugins and integrations with other services out there. If you would like a plugin installed that is not on the below list, please ping User:Skull or User:Arkan in IRC.
- sentry-irc - If you get this to work, let User:Skull know and he will love you longtime
This section goes into the technical setup of the sentry server, Judoon
We're using peer authentication for PostgreSQL, so if you need to get at the command line for sentry's db, use the following:
root@judoon# sudo -u sentry psql
There is only one VHost enabled in Nginx,
Because we're just using the one VHost, Nginx logs are just in the default /var/log/nginx folder.
Redis is still in a default config.
Supervisor is in use to daemonize Gunicorn and Celery.
Config for supervisord lives at
Individual app configs go in
/etc/supervisor/ and can be viewed with
Configuration lives at