Revamp error handling and improve Sentry integration #218
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.
Set up Sentry in order to log messages
Setup the Sentry organization and project
For the project environment, choose “
Vue
”Find and copy the Sentry DSN url in this format: “
https://<first_number>@<second_number>.ingest.de.sentry.io/<id>
” - just a whole DSN urlSet up the env variables:
SENTRY_DSN
# The DSN url mentioned aboveSENTRY_ENV
# The environment so we can filter the issues easily -> “localhost” | “production” | “development”Then we can get the logged issues from the app
We choose the issue in the “
Issues
” taberror
,parentFunctionName
,parentFunctionParams
,accountAddress
,filePath
- in order to find and understand the issue easily (eg. if the params were wrong, which function threw the error, etc.)ReferenceError
section of the Issue on the sentry platformIf we deem some errors not important, and want to limit the number of raised issues (pricing, clutter, etc.) we can additionally ignore them in the config like this:
and those errors wouldn’t be logged on the platform.
This PR fixes #217