search

getsentry / sentry

Developer-first error tracking and performance monitoring
https://sentry.io
Other
38.91k stars 4.17k forks source link

Captured exceptions interpreted as messages #25449

Closed dennisnuhiji closed 3 years ago

dennisnuhiji commented 3 years ago

Important Details

How are you running Sentry?

Saas (sentry.io)

Description

Unhandled JS exceptions that are happening at runtime are being interpreted in the Sentry UI as messages, which makes it hard to find the error since the stack trace is not getting resolved through the source maps.

Steps to Reproduce

  1. Setup NextJS project with Sentry following the with-sentry example
  2. Try and produce an error such as undefined.filter(...
  3. Find the captured error in Sentry Issues dashboard

Good items to include here include:

exceptionAsMessage We can see here that the error with its stack trace is sent as ADDITIONAL DATA arguments and further categorized as Message exceptionAsMessage2

What you expected to happen

To be exception such as this one, which was produced with throw new Error('Second Error') exception

chadwhitacre commented 3 years ago

Thanks @dennisnuhiji, routing to @getsentry/team-webplatform for triage.

kamilogorek commented 3 years ago

We don't have control over https://github.com/vercel/next.js/tree/canary/examples/with-sentry and we just released our own experimental next.js plugin https://docs.sentry.io/platforms/javascript/guides/nextjs/ which we recommend to try, as this is what we are going to iterate over.