Search is available on several features throughout sentry.io such as Issues and Releases.
Looking for information on searching and Discover?
Search queries are constructed using a
key:value pattern, with an optional raw search at the end. Each
key:value pair is a
token and the optional raw search is itself a single
tokens are treated as issue or event properties. The optional raw search is treated as a single
token and searches event titles/messages.
is:resolved user.username:"Jane Doe" server:web-8 example error
In the example above, there are three keys (
server:), but four tokens:
user.username:"Jane Doe" are standard search tokens because both use reserved keywords. See Issue Properties and Event Properties for appropriate keyword usage. The token
server:web-8 is pointing to a custom tag sent by the Sentry SDK. See Custom Tags for more information on how to set tags.
example error is utilizing the optional raw search and is passed as part of the issue search query (which uses a CONTAINS match similar to SQL). When using the optional raw search, you can provide one string, and the query uses that entire string.
Search for Releases supports raw text but not query syntax.
AND between tokens, and use parentheses
() to group conditions.
AND can also be used between non-aggregates and aggregates. However,
Non-aggregates filter data based on specific tags or attributes. For example,
user.username:janeis a non-aggregate field.
Aggregates filter data on numerical scales. For example,
count()is an aggregate function and
count():>100is an aggregate filter.
Some examples of using the
# a valid `OR` query browser:Chrome OR browser:Opera # an invalid `OR` query user.username:janedoe OR count():>100
Also, the queries prioritize
OR. For example, "x
OR z" is the same as "(x
OR z". Parentheses can be used to change the grouping. For example, "x
You can search multiple values for the same key by putting the values in a list. For example, "x:[value1, value2]" will find the the same results as "x:value1
OR x:value2". When you do this, the search returns issues/events that match any search term.
An example of searching on the same key with a list of values:
Currently, you can't use this type of search on the keyword
We recommend you never use reserved keywords (such as
project_id) as tags. But if you do, you must use the following syntax to search for it:
By default, search terms use the
AND operator; that is, they return the intersection of issues/events that match all search terms.
To change this, you can use the negation operator
! to exclude a search parameter.
In the example above, the search query returns all Issues that are unresolved and have not affected the user with the email address
Search supports the wildcard operator
* as a placeholder for specific characters and strings.
In the example above, the search query will match on
browser values like
"Safari 11.0.3", etc.
You may also combine operators like so:
In the above example, the search query returns results which do not have message values like