@sentry/react error boundary eventId does not match event id in the Sentry

[cameronmcefee]

• Review the documentation: https://docs.sentry.io/
• Search for existing issues: https://github.com/getsentry/sentry-javascript/issues
• Use the latest release: https://github.com/getsentry/sentry-javascript/releases
• Provide a link to the affected event from your Sentry account

Package + Version

• "@sentry/react": "^6.17.6",
• "@sentry/tracing": "^6.17.6",

Version:

6.17.6

Description

In the following example, I'm trying to get the id of the event that is captured, so that it will be available to the user that experiences the error to send in a support ticket. However, if I then go search sentry for event.id: <the event id> I can't find the event, and if I track it down manually, the event's ID is not the same.

Is this a bug or do I not understanding what eventId is for?

const MyComponent = () => {
  const [msg, setMsg] = React.useState("Works");

  return (
    <Sentry.ErrorBoundary
      fallback={({ eventId }) => {
        return <p>Search Sentry for <code>event.id: {eventId}</code></p>;
      }}
    >
      <div>{msg}</div>
      <button
        onClick={() => {
          setMsg({ message: "This will break" });
        }}
      >
        Click to trigger error
      </button>
    </Sentry.ErrorBoundary>
  );
};

[AbhiPrasad]

Hey Cameron, thanks for writing in!

I can't find the event, and if I track it down manually, the event's ID is not the same

We just forward the eventID from the captureException call:

sentry-javascript/packages/react/src/errorboundary.tsx

Line 89 in e00b419

const eventId = captureException(error, { contexts: { react: { componentStack } } });

The eventID for an event is generated on the SDK (so we can immediately return it), but there is no guarantee that the event will have been sentry to Sentry. Sentry may have rate-limited the sdk, dropped the event due to network conditions, or the SDK itself may have filtered the error through the Dedupe integration, which prevents sending duplicate errors one after another.

If none of the above applies here, do you mind elaborating with some more details? This is this inconsistency happening locally on the first error sent?

[cameronmcefee]

Thanks @AbhiPrasad! This doesn't apply. I'm working on local dev of a new app, so I've sent less than ten events. All of them show up in Sentry, so I know they are there, hover the ID I get from the captureException call (I made my own error boundary to try it out) is different from the one that's in sentry.

I forgot about the fact that the event ID is generated in the SDK. That makes this particularly strange. Based on that, I took a look at the payload that's being sent and there's a mismatch between the event_id in the payload and the eventId I get back from the captureException call.

[cameronmcefee]

I should also note, I realized that I should be searching for id:<my id> rather than event.id<my id> which appears in my examples. This doesn't have an impact on this issue, but I wanted to call it out since it might become a red herring in debugging.

I don't actually understand why event.id doesn't work, but ¯\(ツ)/¯, that's a separate issue.

[AbhiPrasad]

First of all, the event id management in the SDK is def a little confusing. I opened an issue for us to improve this (so thank you for bringing it up). #4571

To the matter at hand, it's strange that the event IDs are different. @Lms24 would you like to try to help reproduce this? I think its a good starter task - we can then backlog it for anyone to fix once we've identified the problem.

[Lms24]

@AbhiPrasad Sure, sounds good

[github-actions]

This issue has gone three weeks without activity. In another week, I will close it.

But! If you comment or otherwise update it, I will reset the clock, and if you label it Status: Backlog or Status: In Progress, I will leave it alone ... forever!

---

"A weed is but an unloved flower." ― Ella Wheeler Wilcox 🥀

[AbhiPrasad]

Keep - this is still open to investigate