Glitchtip is an application error tracker. It's basically a free, lightweight alternative for Sentry. It even ingests the exact same data as Sentry, so you can just use Sentry's tools to send errors from your application to Glitchtip.

Our instance runs at https://glitchtip.zeus.gent. Read this page to learn how to use it as a user, how to add Glitchtip to your Zeus application, and to maintain Glitchtip as a sysadmin.

To get a Glitchtip account, sign in on https://glitchtip.zeus.gent using Github, or create an account. You won't be able to see anything when logging in, this is normal. Request access to the Zeus WPI organisation by asking someone on Mattermost.

Adding Glitchtip to your application is easy:

1. Create a Glitchtip project
2. Copy the DSN
3. Follow the guides on Sentry on how to add Sentry to your application
4. Use the copied DSN in the configuration
5. Then deploy your application,
6. Send a test message to make sure everything works.

For an example in Rails, check out these commits: adding basic Sentry configuration and only use Sentry in production.

You'll probably want to add a webhook to Mattermost so you know when something goes wrong:

1. On Mattermost, click the icon in the upper left corner
2. Choose for “Integrations”
3. Choose for “Incoming webhooks”
4. Click on “Add incoming webhook” in the top right corner
5. Set up your webhook by giving it a decent name, description, etc.
6. Copy the webhook URL
7. On Glitchtip, in the project settings, create a new project alert
8. Add An Alert Recipient
9. Choose for “General webhook”
10. Paste the URL you copied in step 6

Glitchtip is running on Prattchet, on the Glitchtip user, through docker. Check out the `docker-compose.yml` in `~/glitchtip`.