Apply error-message inbound filters to minidumps

[sentry-junior]

Error-message inbound filters currently do not apply to minidump-derived events, so noisy native crashes cannot be dropped by message pattern at ingest.

Current behavior

• Project inbound filters can discard events by error message using case-insensitive globs that match {exception.type}: {exception.value} on normal error events.
• Docs state that error-message filters do not apply to minidumps: Inbound Filters.
• This was also called out in getsentry/sentry-docs#3139 (Dec 2020): minidump error messages are not available to inbound filters, with no public tracking issue at the time.

Gap

Customers receiving minidump/Crashpad events (for example sdk.name: minidump.crashpad, mechanism.type: minidump) cannot use the existing error-message filter to drop known-noisy patterns such as:

EXCEPTION_BREAKPOINT / 0x...: Fatal Error: EXCEPTION_BREAKPOINT / 0x...

Those events still ingest and consume quota even when a matching filter pattern is configured. Client-side filtering is not always available for crashpad/minidump upload paths.

Request

Support server-side error-message inbound filtering for minidump-derived error events, ideally with the same glob semantics as existing error-message filters, after exception type/value are available on the processed event.

Requested by Sergio Lombana via Junior.

--

View Junior Session in Sentry

[linear-code]

ENG-8258