Star us on GitHub

Error Search

In, you can search for a errors using different attributes on the error group and error instance. The instance is a specific occurance of an error that occurred. Based on the error event, stacktrace, and other attributes, instances are organized into groups. These groups are returned by the search on the Errors search page.

Searching for errors

For general information on searching errors, check out our Search docs.

Default key

The default key for error search is event. If you enter an expression without a key (undefined variable) it will be used as the key for the expression (event="*undefined variable*").

To search for a error event, simply type the text of the message. Given the following error:

sql: statement is closed

We can find this error by typing sql: statement is closed.

The error instances of a specific group and be searched as well. By clicking the "See all instances" button, you can search across instances to get more information on different occurrences of the error group.

Autoinjected attributes

Errors can be searched by the following attributes:

browserUser's browserChrome
client_idClient id associated with the sessionDQbQCEHN0FLuwCeW50AeLI0cH6C4
environmentThe environment specified in the SDKproduction
eventTitle of the errorsql: statement is closed
has_sessionIf the error is tied to a sessiontrue
secure_session_idId of the sessionwh1jcuN5F9G6Ra5CKeCjdIk6Rbyd
service_nameName of the service specified in the SDKprivate-graph
service_versionVersion of the service specified in the SDKe1845285cb360410aee05c61dd0cc57f85afe6da
statusStatus of the error groupRESOLVED
tagTag applied to errordatabase error
trace_idTrace id that contains this log7654ff38c4631d5a51b26f7e637eea3c
typeBroad type of the errorReact.ErrorBoundary
visited_urlURL where the error occurred
Helpful Tips

Use contains, =**, and matches =// operators when searching by visited_url to avoid being too limited by query params. See Searching by Visited URL for more information.