feat: send errors to sentry #60
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
Todmy
reviewed
Jul 12, 2023
Co-authored-by: Dmytro Tolok <[email protected]>
8 tasks
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.
This PR install sentry error monitoring
What it do
capture()inside allcatch, to send the error to sentryThe sendEvents to subscribers errors are not logged, since they fail for reasons out of out control (timeout, not found), and are ignored.
Notes
The required env variables
NODE_ENV, 'SENTRY_DSN' andSENTRY_TRACE_SAMPLE_RATEhave already been added to the server config