Searchable Properties

Sentry's Search provides you with reserved keywords, like is, user, server, and browser, that you can use to search on the properties of issues and events. You can also create custom tags on which to search. Below are canonical lists of all available issue and event search terms.

Issue Properties

Issues are an aggregate of one or more events. Searchable properties include workflow status, assignment, aggregate counts, and age.

Below is a list of issue-level keys and tokens reserved and known to Sentry:

Key/TokenDescription
ageRestrict results to issues created since age. The syntax is similar to the Unix find command. Supported suffixes: m -> minutes, h -> hours, d -> days w -> weeks
age:-24hReturn issues that are new in the last 24 hours.
age:+12hReturn issues older than 12 hours.
age:+12h age:-24hReturn issues created between 12 and 24 hours ago.
assignedFilter on the user which the issue is assigned to. Values can be a user ID (your email address), me for yourself, me_or_none for yourself or no assignee, or #team-name.
assigned_or_suggestedFilter on the user or team to which the issue is assigned or suggested to be assigned. Suggested assignees are determined by matching ownership rules and suspect commits. Values can be a user ID (your email address), me for yourself, me_or_none for yourself or no assignee/suggestions, or #team-name.
bookmarksFilter on the user which the issue is bookmarked by. Values can be your user ID (your email address) or me for yourself.
first-releaseRestrict results to issues first seen within the given release. Exact match on the version of a release, or first-release:latest to pick the most recent release.
hasRestrict results to issues which have any value for a tag.
has:userRestrict results to issues which have a user value for a tag.
isFilter on various properties of an issue.
is:unresolved
is:resolved
is:ignored
Filter on the state of an issue.
is:assigned
is:unassigned
Return issues based on whether they are are assigned or not.
is:linked
is:unlinked
Return issues based on whether they are linked (to an external issue tracker) or not.
lastSeenRestrict results to issues that were last seen since or until a given point in time. Usage is similar to the age token (see above).
lastSeen:+30dReturn issues last seen 30 days ago or more.
lastSeen:-2dReturn issues last seen within the last two days.
timesSeenRestrict results to issues that have been seen exactly, at least, or at most some number of times.

An exact match token: timesSeen:10.

Upper or lower bounds tokens: timesSeen:>10, timesSeen:>=10, timesSeen:<10, timesSeen:<=10

Event Properties

Events are the underlying event data captured using Sentry SDKs (read: errors and transactions).

When searching on event properties within the Issues page, the search will return any issue that has one or more events matching the supplied event filters.

Below is a list of event-level keys and tokens reserved and known to Sentry:

Key/TokenDescription
locationRestrict results to the events with a matching location.
messageRestrict results to events with a matching message.
environmentRestrict results to events tagged with the matching environment.
releaseRestrict results to events tagged with the matching release. You can create a token with an exact match on the version of a release, or release:latest to pick the most recent release.
release.package
release.version
release.build
Restrict results to events tagged with the matching semantic version. Supports ranges and wildcards. Learn more in Sorting & Filtering Releases.
release.stageRestrict results to releases that are tagged with the matching release stage. See Filtering Releases for supported values.
transactionRestrict results to events tagged with a URL template/job name.
geo.country_code
geo.region geo.city
Restrict results to events triggered by a geographic area.
http.method
http.referer
http.url
Restrict results based on the HTTP request context.
user.id user.email
user.username
user.ip
Restrict results to events affecting a given user.
event.timestampRestrict results to events that occurred at the given timestamp. This filter can be passed twice to provide a range.

Events occurred on January 2, 2016: event.timestamp:2016-01-02

Events between 01:00 and 02:00 (UTC): event.timestamp:>=2016-01-02T01:00:00 event.timestamp:<2016-01-02T02:00:00

The following comparative operators are available: greater than (>), greater than or equal (>=), less than (<), less than or equal (<=)
device.arch
device.battery_level
device.brand
device.charging
device.locale
device.model_id
device.name
device.online
device.orientation
device.simulator
device.uuid
Restrict results to events tagged with a specific device attribute.
os.build
os.kernel_version
Restrict results to events tagged with a specific operating system property.
stack.abs_path
stack.filename
stack.function
stack.module
stack.package
stack.stack_level
stack.lineno
Restrict results to events with a matching stack property.

For Native SDK users, stack.package is the Native equivalent for stack.module. For more details about enhancing search, see the full documentation on adding context and customizing tags.
error.type
error.value
error.mechanism
error.handled
Restrict results to events with a matching error property.

Custom Tags

Additionally, you can use any tag you’ve specified as a token. Tags are various key/value pairs that get assigned to an event, and you can use them later as a breakdown or quick access to finding related events.

Most SDKs generally support configuring tags by configuring the scope.

Several common uses for tags include:

  • The hostname of the server
  • The version of your platform (for example, iOS 5.0)
  • The user’s language
Help improve this content
Our documentation is open source and available on GitHub. Your contributions are welcome, whether fixing a typo (drat!) to suggesting an update ("yeah, this would be better").