Sentry doesnt report server side errors
See original GitHub issueVersion
@nuxtjs/sentry: ^5.13.6
nuxt: 2.15.7
Sentry configuration
sentry: {
dsn: process.env.SENTRY_DSN || null,
debug: devMode,
},
Reproduction Link
private repo, can’t do
Steps to reproduce
check out of sentry.server.config.js
in the .nuxt
build folder. DSN is missing:
/* eslint-disable */ export const config = {"environment":"development","release":"d83291467b1702f2e8c933a096d4cd84e49dc965"}
What is Expected?
process.sentry.captureException
works
What is actually happening?
doesn’t work
Issue Analytics
- State:
- Created 2 years ago
- Comments:9 (4 by maintainers)
Top Results From Across the Web
sentry/nextjs doesn't report server-side errors #6485 - GitHub
Steps to Reproduce. We've noticed that at some point Sentry stopped reporting next.js server-side errors on Vercel. I tried example from scratch ...
Read more >Troubleshooting for Next.js - Sentry Documentation
By default, Sentry does not capture errors when a resource (like an image or a css file) fails to load. If you would...
Read more >Advanced Features: Error Handling - Next.js
Error Handling. This documentation explains how you can handle development, server-side, and client-side errors. Handling Errors in Development.
Read more >Error Tracing | Sentry Documentation
With error tracing, you can correlate errors from multiple services and uncover a significant story surrounding a break. Using a unique identifier allows ......
Read more >Sentry with SSR - javascript - Stack Overflow
Client -side is wrapped in special HOC, called in most cases Error Boundary. React passes up an error to the root component of...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
You could check whether on the client side a network request is dispatched to Sentry endpoint on triggering an error.
Based on the comments I’m assuming it was not a module’s issue.