Sentry event showing all zeros for Trace ID (contexts.trace.span_id) causing processing error #18037
Description
Is there an existing issue for this?
- I have checked for existing issues https://github.com/getsentry/sentry-javascript/issues
- I have reviewed the documentation https://docs.sentry.io/
- I am using the latest SDK release https://github.com/getsentry/sentry-javascript/releases
How do you use Sentry?
Sentry Saas (sentry.io)
Which SDK are you using?
@sentry/remix
SDK Version
10.21.0
Framework Version
remix @ 2.16.5
Link to Sentry event
https://promi-d6.sentry.io/issues/6422520377/events/d5f0306e73b64887ba085086d6f3b704/
Reproduction Example/SDK Setup
Below is our sentry init block
Sentry.init({
dsn: "__DSN__",
sendDefaultPii: true,
tracesSampleRate: 0.01,
replaysSessionSampleRate: 0.01,
replaysOnErrorSampleRate: 1,
attachStacktrace: true,
// Will be replaced by Vite at build time
environment: __SENTRY_ENVIRONMENT__,
integrations: [
Sentry.captureConsoleIntegration({
levels: ["warn", "error"],
}),
],
});
We capture events using Sentry.captureException. This started happening after we upgraded the sentry/remix version from v8 to v10 (we followed the upgrade guide of v8->v9 and v9->v10)
Steps to Reproduce
When sending event by calling Sentry.captureException we see that those events appeared in sentry with processing error.
Name: contexts.trace.span_id
Value: 0000000000000000
Reason: not a valid span id
Expected Result
No processing error
Actual Result
Most events have this processing error showed up saying contexts.trace.span_id is all zeros.
Also Trace Details showing the Trace ID as all zeros.
Additional Context
Tip: React with 👍 to help prioritize this issue. Please use comments to provide useful context, avoiding +1 or me too, to help us triage it.