Aggregated exceptions search not working.

[rodolfoBee]

Environment

SaaS (https://sentry.io/)

Steps to Reproduce

1. Send a aggregated exception such as:

2. Try to search for InternalServerError on the issues page
3. Try to search for ReplyError on the issues page

Expected Result

The events/issues are found for both 2 and 3.

Actual Result

No event is found when searching for InternalServerError, only ReplyError gives results.

The current workaround is to search using error.type:InternalServerError.

Product Area

Issues

Link

No response

DSN

No response

Version

No response

[getsantry]

Assigning to @getsentry/support for routing ⏲️

[getsantry]

Routing to @getsentry/product-owners-issues for triage ⏲️

[ceorourke]

Hi @rodolfoBee how do you send an aggregated exception?

[johanholmerin]

Original reporter here. I encountered this in a Node.js project where we add additional information to errors by wrapping them using Error#cause.

} catch (error) {
  throw new InternalServerError('Unknown error', { cause: error });
}

We send the aggregated error to Sentry using captureException(error) and both the errors show up in the same issue in Sentry, it's just not possible to search for InternalServerError.

[roggenkemper]

thanks for bringing this up, will add it to our backlog to take a look at this bug.

[lobsterkatie]

This should (partially) be fixed by getsentry/sentry-javascript#10850, which fixes it so that we don't ignore the top error in a chain of errors linked by the cause property. I say "partially," though, because that will make searching on InternalServerError work again, but will break the ability to search on the cause error's data. (I swear there's a different issue about that, from before the problem reported here arose, but I cannot for the life of me find it. I know it's not this issue, because I know it existed as of mid-July (months before this one), because I have a WIP branch on the topic from around that time. Very mysterious.)

In any case, I've been doing some other work around linked issues, so I'll see if I can pull this into that project and pick that branch back up.