-
-
Notifications
You must be signed in to change notification settings - Fork 110
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix Sentry config on the server side #377
Conversation
…see if it fixes the issue with flush() timeout
✅ Deployment SUCCESS |
✅ E2E tests SUCCESS for commit d8ca4fd previously deployed at https://nrn-v2-mst-aptd-at-lcz-sty-c1-hbha0r12t-unly-oss.vercel.app |
…t Sentry when using configureReq
…a from req object)
✅ Deployment SUCCESS |
✅ E2E tests SUCCESS for commit 9f68fce previously deployed at https://nrn-v2-mst-aptd-at-lcz-sty-c1-2nzuqx0c3-unly-oss.vercel.app |
✅ Deployment SUCCESS |
✅ E2E tests SUCCESS for commit f32f876 previously deployed at https://nrn-v2-mst-aptd-at-lcz-sty-c1-2x6s45mvm-unly-oss.vercel.app |
✅ Deployment SUCCESS |
✅ Deployment SUCCESS |
✅ E2E tests SUCCESS for commit d6a21b1 previously deployed at https://nrn-v2-mst-aptd-at-lcz-sty-c1-p5jzaerca-unly-oss.vercel.app |
* Re-export Sentry from init (DX) and call init from error endpoint to see if it fixes the issue with flush() timeout * Improve sentry init documentation + rollback to timeout 2s + auto-init Sentry when using configureReq * Implement better error handling on _error page (enrich Sentry metadata from req object) * Fix 404 error handling and reporting to Sentry * Improve documentation about error handling * Upgrade Sentry to latest (minor)
✅ E2E tests SUCCESS for commit d6a21b1 previously deployed Storybook static site at https://nrn-v2-mst-aptd-at-lcz-sty-storybook-duh07eokz-unly-oss.vercel.app |
Events aren't properly reported to Sentry for API endpoints, might have broken something during refactoring.
Fixes: