Discover

Introduction

Discover lets you query raw event data in Sentry, across any number of projects within your organization.

Using the query builder

Summarize

Select the event attributes you want to summarize over.

If there are no aggregations present, raw event data is returned and this selects the columns we want to display.

If there are aggregations in the query, this is effectively a groupby clause.

See here for the list of fields available.

Aggregations

Leave blank if you want a table of raw event data, otherwise the selected function is run over the event attributes selected in Summarize above.

Available functions are:

  • count - count of rows
  • uniq - count of distinct rows
  • avg - mathematical average on a number field
Conditions

You can use conditions to filter events from results by field (see here for the list of fields).

All conditions are joined with AND syntax.

The condition operators available are:

  • IS NULL, IS NOT NULL (for all column types)
  • =, !=, LIKE, NOT LIKE (for strings)
  • Values used with LIKE are case sensitive and can be used with wildcard characters
  • e.g. exception_stacks.type LIKE Validation%
  • >, >=, <, <= (for numbers)
Order by

This field should update automatically as you update your query parameters to list allowable aggregations or fields for sorting.

Limit

Any integer between 1 and 1000 is valid.

Project selector

By default Discover searches events across all projects that you are a member of within the organization.

Date range

You need to provide either a relative date (e.g. last 14 days) or an explicit start and end date.

This defaults to the last 14 days.

In most cases data is retained by Sentry for 90 days.

Saved queries

Any user within the organization can create, view, edit and delete the saved queries for that organization.

Save a query by clicking “save” in the sidebar. The query will be saved with an auto-generated name.

View all saved queries for the organization by navigating to the saved query tab.

List of event fields

Events have a number of built in fields as well as custom tags.

Standard fields

General
  • id (string)
  • issue.id (number)
  • project.id (number)
  • project.name (string)
  • timestamp (datetime)
  • platform (string)
  • message (string)
  • release (string)
User attributes
  • user.id (string)
  • user.username (string)
  • user.email (string)
  • user.ip (string)
SDK
  • sdk.name (string)
  • sdk.version (string)
OS
  • os.build (string)
  • os.kernel_version (string)
Device
  • device.name (string)
  • device.brand (string)
  • device.locale (string)
  • device.uuid (string)
  • device.model_id (string)
  • device.arch (string)
  • device.battery_level (number)
  • device.orientation (string)
  • device.simulator (string)
  • device.online (string)
  • device.charging (string)
Geo
  • geo.country_code (string)
  • geo.region (string)
  • geo.city (string)
HTTP
  • http.method (string)
  • http.url (string)
Stack traces
  • error.type (string)
  • error.value (string)
  • error.mechanism (string)
  • error.handled (string)
  • stack.abs_path (string)
  • stack.filename (string)
  • stack.package (string)
  • stack.module (string)
  • stack.function (string)
  • stack.in_app (boolean)
  • stack.colno (number)
  • stack.lineno (number)
  • stack.stack_level (number)

Commonly used tags

These tags are commonly used / implemented in Sentry’s SDKs

General
  • level (string)
  • logger (string)
  • server.name (string)
  • transaction (string)
  • environment (string)
  • site (string)
  • url (string)
  • app.device (string)
  • device.family (string)
  • runtime (string)
  • runtime.name (string)
  • browser (string)
  • browser.name (string)
  • os (string)
  • os.name (string)
  • os.rooted (boolean)

Additionally, any custom user-defined tags can also be queried in the same way

On this page