Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Improve Sentry tracing #305

Open
Vadorequest opened this issue Apr 1, 2021 · 0 comments · May be fixed by #370
Open

Improve Sentry tracing #305

Vadorequest opened this issue Apr 1, 2021 · 0 comments · May be fixed by #370
Assignees
@Vadorequest
Labels
enhancement New feature or request

Comments

@Vadorequest
Copy link
Member

Vadorequest commented Apr 1, 2021 •
edited
Loading

There seems to be a new way to trace browser issues.

https://docs.sentry.io/platforms/javascript/guides/nextjs/#configure

Benefits:

  • Automatic Error Tracking with source maps for both JavaScript and TypeScript
  • Events enriched with device data
  • Breadcrumbs created for outgoing HTTP request with XHR and Fetch, and console logs
  • Release Health for tracking crash-free users and sessions
  • Automatic Performance Monitoring for both the client and server, from version 6.5.0
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@Vadorequest Vadorequest

Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Migrating to @sentry/nextjs (removing @sentry/browser and @sentry/node) UnlyEd/next-right-now
1 participant
@Vadorequest