feat(sentry): capture error in Sentry when departure fetch fails #1754
+68
−9
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.
Denne PR-en fikser sentry-konfigurasjonen vår så dsn-variabelen også er tilgjengelig på klientens browser (og vi får tak i feil derfra).
I tillegg legges det på en custom error-catching når fetch fra journeyplanner feiler, timer ut eller ikke returnerer noe data.
edit: legger også på custom feilmelding når server-side fetch feiler.
For å teste dette lokalt må du først:
enabled: process.env.NODE_ENV !== 'development',
fra de tre sentry-config-fileneNEXT_PUBLIC_SENTRY_DSN_URL
så må du kræsje fetch, f eks ved å endre timeout-verdien til et veldig lavt tall.
Bør dukke opp i sentry: