Enable Sentry for TAP #4191
Draft
Enable Sentry for TAP #4191
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
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.
Description
Enable Sentry error logging and tracing for TAP service.
Enables for idfint & idfdev. If left disabled TAP services for other environments should continue to work without any noticeable change.
Jira Issue
https://rubinobs.atlassian.net/browse/DM-48801
Related PR in TAP service
lsst-sqre/lsst-tap-service#127
Tests
I've tested on an dev & int with SENTRY_DSN enabled, and then the same build with SENTRY_DSN disabled in phalanx to ensure that tracing doesn't get sent in the second case
TODO Before merge
Set image of TAP service to new release before merging