A series of

  • 1 minute Quick use of The latest version of Docker Sentry-CLI – create version
  • Quick use of Docker start Sentry-CLI – 30 seconds start Source Maps
  • Sentry For React
  • Sentry For Vue
  • Sentry-CLI usage details
  • Sentry Web Performance Monitoring – Web Vitals
  • Sentry Web performance monitoring – Metrics
  • Sentry Web Performance Monitoring – Trends
  • Sentry Web Front-end Monitoring – Best Practices (Official Tutorial)
  • Sentry Backend Monitoring – Best Practices (Official Tutorial)
  • Sentry Monitor – Discover Big data query analysis engine
  • Sentry Monitoring – Dashboards Large screen for visualizing data
  • Sentry Monitor – Environments Distinguishes event data from different deployment Environments
  • Sentry monitoring – Security Policy Reports Security policies

directory

  • grammar
    • useOR 和 AND
    • The sameKeyMultiple values of
    • explicitTaggrammar
    • senior
      • To rule out
      • Wildcards (*)
  • Searchable properties
    • Issueattribute
    • Eventattribute
    • The customTag
  • Saved search
    • recommendation
    • Fixed search
      • Change fixed search
      • Fixed recommendation search
    • Organization-wide saved searches
      • Create an organization-wide saved search
      • Deletes organization-wide saved searches

grammar

The search query is built using the key:value pattern, followed by an optional raw search. Each key:value is a token, and the optional raw search is itself a token. Key: Value tokens are treated as issue or event attributes. The optional raw search is treated as a single token and searches for event title/message.

Such as:

is:resolved user.username:"Jane Doe" server:web-8 example error
Copy the code

In the example above, there are three keys (is:, user.username:, server:), but there are four tokens:

  • is:resolved
  • user.username:"Jane Doe"
  • server:web-8
  • example error

Token is:resolved and user.username:”Jane Doe” are standard search tokens because both use reserved keywords. For appropriate keyword usage, see the Issue attribute and the Event attribute. Token Server: Web-8 points to a custom tag sent by the Sentry SDK.

The Token example incorrectly uses an optional raw search and is passed as part of an issue search query (using SQL like CONTAINS matches). With the optional raw search, you can supply a string and the query will use the entire string.

useOR 和 AND

The OR AND search criteria apply only to Discover, Performance, AND Metric Alerts.

OR AND AND are used between tokens, AND conditions are grouped using parentheses (). AND can also be used between non-aggregates AND aggregates. But, OR can’t.

  • Non-aggregation filters data based on specific tags or attributes. For example,user.username:janeIs a non-aggregate field.
  • On a numerical scale (numerical scales) to aggregate filtered data. For example,count()Is an aggregate function, andcount():>100It’s an aggregate filter.

Some examples of using OR conditions:

# a valid 'OR' query browser:Chrome OR browser:Opera # an invalid 'OR' query user.username: Janedoe OR count():>100Copy the code

In addition, the query takes precedence over AND before OR. For example, “x AND y OR z” is the same as “(x AND y) OR z”. Parentheses can be used to change grouping. For example, “x AND (y OR z)”.

The sameKeyMultiple values of

You can search for multiple values of the same key by placing values in a list. For example, “x:[value1, value2]” will find the same result as “x:value1 OR x:value2”. When you do this, the search returns issues/events that match any of the search terms.

Example of searching for the same key using a list of values:

Release: [12.0, 13.0]Copy the code

Currently, you cannot use this type of search for the keyword is.

explicitTaggrammar

We recommend that you never use reserved keywords (such as project_id) as tags. But if you do, you must search using the following syntax:

tags[project_id]:tag_value
Copy the code

senior

To rule out

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! Exclude search parameters.

is:unresolved ! user.email:[email protected]Copy the code

In the example above, the search query returns all unresolved Issues that do not affect users with email addresses [email protected].

Wildcards (*)

The search supports wildcard * as a placeholder for specific characters and strings.

browser:"Safari 11*"
Copy the code

In the example above, the search query will match the browser value, such as “Safari 11.0.2”, “Safari 11.0.3”, and so on.

You can also combine operators like this:

! message:"*Timeout"Copy the code

In the example above, search for message values that are not returned by the query, such as ConnectionTimeout, ReadTimeout, and so on.

Searchable properties

Sentry’s search gives you reserved keywords, such as IS, User, Server, and browser, that you can use to search for issue and Event properties. You can also create custom tags to search for. Below is a canonical list of all available search terms for issues and events.

Issueattribute

An Issue is a collection of one or more events. Searchable attributes include Workflow Status, Assignment, Aggregate Counts, and Age.

Here is a list of keys and tokens at the Sentry level that are reserved and known:

Key/Token describe
age Constrained result selfageSince producedissue. Syntax is similar toUnix findCommand. Suffixes:m -> minutes.h -> hours.d -> days.w -> weeks
age:-24h Return to the past24New within hoursissue.
age:+12h Return more than12Hours ofissue.
age:+12h age:-24h Return more than12 到 24Created hours agoissue.
assigned screeningissueUser assigned to. Values can beuser ID(youremailAddress),meOn your own behalf,me_or_noneOn behalf of yourself or no receiver, or#team-name.
assigned_or_suggested filterassigned 或 suggestedAssign problem users or teams. The proposed receiver should be matchedOwnership RulesandSuspect commitsSure. Values can beuser ID(youremailAddress),meOn your own behalf,me_or_noneRepresent yourself or no receiver/proposal, or#team-name.
bookmarks Filter forissueBookmark users. Values can beuser ID(youremailAddress) ormeRepresent yourself.
first-release Restrict the results to those first occurring in a given versionissue. Matches the release version exactly, orfirst-release:latestSelect the latest version.
has Restrict the result to having anytagThe value of theissue.
has:user Restrict the result to having tagsuserThe value of theissue.
is screeningissueProperties of.
is:unresolved

is:resolved

is:ignored		 According to theissueState filter.
is:assigned

is:unassigned		 Based on whether it has been allocatedissuereturnissue.
is:linked

is:unlinked		 According to theissueWhether to link (to the outsideissueTracker) returnsissue.
lastSeen Limit the result to from (since) or until (until) The last problem at a given point in time. Usage is similar toageToken (see above).
lastSeen:+30d returnissueThe last time he was seen30Days ago or more.
lastSeen:-2d Returns the last two daysissue.
timesSeen Limit the results to precisely, at least, or at most certain timesissueOn.

A perfect match:timesSeen:10.

Upper or lower limittoken:timesSeen:>10, timesSeen:>=10, timesSeen:<10, timesSeen:<=10

Eventattribute

Events are low-level event data captured using the Sentry SDK (read: Errors and Transactions).

When you search for event properties on the “Issues” page, the search returns any Issues with one or more events that match the provided event filter.

The following is a list of Sentry’s reserved and known Event-level keys and tokens:

Key/Token describe
location Restrict the result to having a matchlocationIn the event.
message Restrict the result to having a matchmessageIn the event.
environment Restrict the result to matchesenvironmentTagged events.
release Limit the result to events with matching version tags. You can create one that exactly matches the release versiontokenOr,release:latestSelect the latest version.
release.package

release.version

release.build		 Limit the result to events marked with matching semantic versions. Support for ranges and wildcards (*).
release.stage Limit the results to those with matching release phase tagsrelease.
transaction Limit the results to markedURL template/jobName of the event.
geo.country_code

geo.region geo.city		 Limit the results to events that are triggered by geographic regions.
http.method

http.referer

http.url		 Restrict the results based on the HTTP request context.
user.id user.email

user.username

user.ip		 Limit the results to events that affect a given user.
event.timestamp Limits the result to events that occur at a given timestamp. The filter can be passed twice to provide a range.

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

01:00 和 2:00(UTC) events between:event.timestamp:>=2016-01-02T01:00:00 event.timestamp:<2016-01-02T02:00:00

The following comparison operators can be used: greater than (>), greater than or equal to (> =), less than (<), less than or equal to (< =)
device.arch

device.battery_level

device.brand

device.charging

device.locale

device.model_id

device.name

device.online

device.orientation

device.simulator

device.uuid		 Limit the result to events marked with specific device attributes.
os.build

os.kernel_version		 Limit the result to events marked with a specific operating system attribute.
stack.abs_path

stack.filename

stack.function

stack.module

stack.package

stack.stack_level

stack.lineno		 Limit the result to events with matching stack attributes.

forNative SDKThe user,stack.package 是 stack.module 的 NativeEquivalent terms.
error.type

error.value

error.mechanism

error.handled		 Limit the result to events with matching error attributes.

The customTag

In addition, you can use any tag that you specify as a token. Tags are the various key/value pairs assigned to events that you can use later for segmentation or quick access to find related events.

Most SDKS typically support configuring a tag by configuring a scope.

Several common uses of tags include:

  • The server’shostname
  • Your platform version (for example,IOS 5.0)
  • The user’slanguage

Saved search

In the “Saved Searches” TAB of Issues, you can access recommended Searches, fix the Searches you think are most useful, and leverage organization-wide Saved Searches.

recommendation

Recommended search is a common search term we think you might use. These pre-performed Searches are listed under “Recommended Searches” in the “Saved Searches” drop-down list, and in the order of your most recent use of them.

Fixed search

You can fix the search, and it will be the default view you see on the Issues page. Fixed searches are visible only to you and are relevant to your project.

  1. Type the search term in the search bar.

2. Click the pushpin icon next to the search.3. After fixation,SentryWill add the search to"Saved Searches"In the drop-down list. The search label in the text will be displayed as"My Pinned Search".

Change fixed search

To change your fixed search:

  1. Select your fixed search. Unclick the pushpin icon. Your default search will return tois:unresolved.
  2. Run another search. Click the pushpin icon. As a"My Pinned Search"The query will now become the new fixed query, replacing the original query.

Fixed recommendation search

You can fix the recommended search just like any other search. When you select the recommended search and the recommended search query populates the search bar, set it.

Organization-wide saved searches

Create an organization-wide saved search

Owners and managers can create persistent views for their organizations by creating custom save searches. These saved searches are not associated with specific projects, but with all projects (and users) throughout the organization.

  1. Type search in the search bar and click the Action menu (three dots). choose"Create Saved Search".

  1. In the openmodalTo name and set the searchissuesSort order of a list. You can also update the query here. And then click"Save".

  1. The view will then become"Saved Search"Part of the drop down list.

Deletes organization-wide saved searches

This operation only applies to the organization owner or Manager.

When you hover over a custom saved Search, the trash can icon is displayed next to the search name. Click the trash can icon to remove the custom saved search from the drop-down list.