Glob Syntax inconsistent in Inbound Filters

[kpujjigit]

Environment

SaaS (https://sentry.io/)

Steps to Reproduce

Example: say we want to filter out all errors beginning with TypeError1234

1. Access Inbound Filters under Project Settings > Inbound Filters > Error Message
2. Trail the Error Message in inbound filters with a wildcard * as intended -> TypeError1234*

Expected Result

All errors beginning with TypeError1234 are filtered.

Actual Result

Trailing an Error Message in inbound filters with a wildcard * as intended, will not work.

Instead, the message needs to be encapsulated in wildcards, like *TypeError1234* even if it's the start of the message.

Product Area

Settings

Link

No response

DSN

No response

Version

No response

[getsantry]

Assigning to @getsentry/support for routing ⏲️

[getsantry]

Routing to @getsentry/product-owners-ingestion-and-filtering for triage ⏲️

[Dav1dde]

This is historic and probably too late to change now because it involves to many already configured rules,

Relay prepends the message which is a matched against the glob with the exception type, e.g. {"ty": "Error", "value": "Foobar XXX"} means your glob must be Error: Foobar* not just Foobar*.

Code here: https://github.com/getsentry/relay/blob/f981d606ef93ab106d902bd4aa5f92c88d56cda8/relay-filter/src/error_messages.rs#L35