Re-enable Sentry

this MR with the deployment changes here https://git.ligo.org/computing/gracedb/deployment/-/merge_requests/4 re-enables Sentry monitoring

requested review from @stuart.anderson, @pfc, @patrick.godwin, and @sara.vallero

I deployed this change to gracedb-dev and manually triggered a ValueError by editing the container's source code on the fly (yolo) and it got picked up by sentry:

requested review from @pb

approved this merge request

added 1 commit

• 3bfa8368 - try and get sentry to ignore aws xray SegmentNotFoundExceptions

Compare with previous version

Thanks @sara.vallero. This has been running on gracedb-dev/test/playground.

The next steps to get this onto production are:

1. reviewer approval of the deployment changes (https://git.ligo.org/computing/gracedb/deployment/-/merge_requests/4)
2. new point release of the server code with the above changes

added 7 commits

• 3bfa8368...223ac5ff - 3 commits from branch master
• 729feac7 - enable sentry and define env across tiers
• 9582c84b - get sentry dsn from docker secrets
• cb66c454 - upgrade sentry-sdk
• 303e473f - try and get sentry to ignore aws xray SegmentNotFoundExceptions

Compare with previous version

removed review request for @patrick.godwin

merged

mentioned in merge request !201 (merged)