[back-end] Add Glitchtip error tracking #93
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
rogup
force-pushed
the
glitchtip-back-end
branch
from
8826818 to
c339750
Compare
wu-lee
reviewed
Nov 24, 2024
wu-lee
reviewed
Nov 24, 2024
|
Apart from the very minor points in the comments, this is all good - will merge it myself as you suggest, |
wu-lee
force-pushed
the
glitchtip-back-end
branch
from
c339750 to
dbee63a
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What? Why?
This will allow us to track uncaught exceptions and also 4xx and 5xx HTTP errors, viewable on the Glitchtip dashboard https://app.glitchtip.com/digital-commons-coop/issues?project=9203
(I included 4xx errors since we shouldn't really be hitting these if the FE is supplying the correct data)
It would be nice to notify Element devops channel but doesn't look like Glitchtip supports this yet. We could probably get it working eventually though, with some sort of workaround using webhooks or Matrix bots.
I've tested that this works on my local machine and the events are being picked up on the Glitchtip console
Deployment notes
Need to change
export GLITCHTIP_KEY=<key>in the deploy.env toexport FE_GLITCHTIP_KEY=<key>;export BE_GLITCHTIP_KEY=<key>;when deploying to the servers.