Sentry: Regex search

[hermansje]

When filtering events, it would be useful to be able to use regex.
In a web project, using regex you could match events from all versions of Chrome, or from a subset of URLs.

[dcramer]

It's unlikely we're going to offer this any time soon (or potentially ever) as it's very expensive to allow this kind of search and Sentry operates on a very large scale of data.

[hermansje]

I understand the difficulty. Is there a more realistic way of implementing non-exact searches?
Would it be less prohibitive for performance if just a wildcard at the end was allowed?

[dcramer]

@hermansje so we do "CONTAINS" today, but we only include specific segments, and we dont let you do that kind of match on tags. I guess it really depends. For example, we have 'browser.name:Chrome' now which solves one of your cases.

[DennisBecker]

What about filtering all issues for domain www.example.com or local.example.com? That could help to identify issues instead of complete URLs

[deeTEEcee]

It's unlikely we're going to offer this any time soon (or potentially ever) as it's very expensive to allow this kind of search and Sentry operates on a very large scale of data.

I feel like this is actually something worth working towards. Seems like a very common search case for anything production-level.

[dcramer]

The latest iteration of search allows wildcards in values which solves the common cases we've seen reported.

[Herz3h]

So something like https://example.com/* should work ? @dcramer

I tested it and it doesn't work for me, but maybe my sentry docker isn't updated.

[dcramer]

It is implemented in our new search which is in master / on sentry.io.

[mpistrang]

It is great to hear that wildcard search is becoming a standard feature! I'm having trouble finding this in the release notes. Is there a minimum version of Sentry I need to upgrade to in order to take advantage of this? Is there a commit or pull request this issue could be linked to?

Thanks!

[dcramer]

It’s in 9.x (master) but it requires new infrastructure that we don’t document today. It’s not available with our sql-based search.

[mpistrang]

Thanks for the info and the quick reply!

[udlose]

It's unlikely we're going to offer this any time soon (or potentially ever) as it's very expensive to allow this kind of search and Sentry operates on a very large scale of data.

Respectfully, Splunk has offered something similar for years now. I can't believe that Sentry is not able to do this. Splunk can capture WAY MORE data with all of the forwarders and kinds of data hosting it offers and yet is able to have a very performant search mechanism.