List of breadcrumbs recorded before this event.

Information about the system SDK (e.g. iOS SDK).

Meta data for event processing and debugging.

Errors encountered during processing. Intended to be phased out in favor of
annotation/metadata system.

Optional ISO C standard error code.

A Mach Exception on Apple systems comprising a code triple and optional descriptions.

An NSError on Apple systems comprising code and signal.

Information on the POSIX signal.

Operating system or runtime meta information.

Mechanism by which this exception was generated and handled.

A possible lock (java monitor object) held by this frame.

Required. A non-empty list of stack frames. The list is ordered from caller to callee, or
oldest to youngest. The last frame is the one creating the exception.

Stack trace containing frames of this exception.

One or multiple chained (nested) exceptions.

Custom parameterized message for this event.

Information about a web request that occurred during the event.

List of installed and loaded SDK packages. Optional.

A list of packages that were installed as part of this SDK or the activated integrations.
Each package consists of a name in the format source:identifier and version. If the
source is a Git repository, the source should be git, the identifier should be a
checkout link and the version should be a Git reference (branch, tag or SHA).

Information about the Sentry SDK that generated this event.

A possible lock (java monitor object) held by this frame.

Required. A non-empty list of stack frames. The list is ordered from caller to callee, or
oldest to youngest. The last frame is the one creating the exception.

Event stacktrace.

DEPRECATED: Prefer threads or exception depending on which is more appropriate.

Represents a collection of locks (java monitor objects) held by a thread.

A map of lock object addresses and their respective lock reason/details.

A possible lock (java monitor object) held by this frame.

Required. A non-empty list of stack frames. The list is ordered from caller to callee, or
oldest to youngest. The last frame is the one creating the exception.

Stack trace containing frames of this exception.

The thread that crashed with an exception should not have a stack trace, but instead, the thread_id attribute should be set on the exception and Sentry will connect the two.

Threads that were active when the event occurred.

A list of changes prior to the final transaction name.

This list must be empty if the transaction name is set at the beginning of the transaction
and never changed. There is no placeholder entry for the initial transaction name.

Additional information about the name of the transaction.

Approximate geographical location of the end user or device.

Information about the user who triggered this event.

The sentry v7 event structure.

Application information.

App context describes the application. As opposed to the runtime, this is the actual
application that was running and carries metadata about the current session.

Legacy apple debug images (MachO).

This was also used for non-apple platforms with similar debug setups.

The Breadcrumbs Interface specifies a series of application events, or "breadcrumbs", that
occurred before an event.

An event may contain one or more breadcrumbs in an attribute named breadcrumbs. The entries
are ordered from oldest to newest. Consequently, the last entry in the list should be the last
entry before the event occurred.

While breadcrumb attributes are not strictly validated in Sentry, a breadcrumb is most useful
when it includes at least a timestamp and type, category or message. The rendering of
breadcrumbs in Sentry depends on what is provided.

The following example illustrates the breadcrumbs part of the event payload and omits other
attributes for simplicity.

{
"breadcrumbs": {
"values": [
{
"timestamp": "2016-04-20T20:55:53.845Z",
"message": "Something happened",
"category": "log",
"data": {
"foo": "bar",
"blub": "blah"
}
},
{
"timestamp": "2016-04-20T20:55:53.847Z",
"type": "navigation",
"data": {
"from": "/login",
"to": "/dashboard"
}
}
]
}
}

Web browser information.

POSIX signal with optional extended data.

Error codes set by Linux system calls and some library functions as specified in ISO C99,
POSIX.1-2001, and POSIX.1-2008. See
errno(3) for more information.

List of installed and loaded SDK packages. Optional.

A list of packages that were installed as part of this SDK or the activated integrations.
Each package consists of a name in the format source:identifier and version. If the
source is a Git repository, the source should be git, the identifier should be a
checkout link and the version should be a Git reference (branch, tag or SHA).

The SDK Interface describes the Sentry SDK and its configuration used to capture and transmit an event.

An installed and loaded package as part of the Sentry SDK.

The previous route in the application

Set by React Native SDK.

The current route in the application.

Set by React Native SDK.

The arbitrary data on the trace.

Information about the system SDK (e.g. iOS SDK).

Debugging and processing meta information.

The debug meta interface carries debug information for processing errors and crash reports.
Sentry amends the information in this interface.

Example (look at field types to see more detail):

{
"debug_meta": {
"images": [],
"sdk_info": {
"sdk_name": "iOS",
"version_major": 10,
"version_minor": 3,
"version_patchlevel": 0
}
}
}

Device information.

Device context describes the device that caused the event. This is most appropriate for mobile
applications.

An event processing error.

Optional ISO C standard error code.

A Mach Exception on Apple systems comprising a code triple and optional descriptions.

An NSError on Apple systems comprising code and signal.

Information on the POSIX signal.

Operating system or runtime meta information.

Mechanism by which this exception was generated and handled.

A possible lock (java monitor object) held by this frame.

Required. A non-empty list of stack frames. The list is ordered from caller to callee, or
oldest to youngest. The last frame is the one creating the exception.

Stack trace containing frames of this exception.

A single exception.

Multiple values inside of an event represent chained exceptions and should be sorted oldest to newest. For example, consider this Python code snippet:

try:
raise Exception("random boring invariant was not met!")
except Exception as e:
raise ValueError("something went wrong, help!") from e

Exception would be described first in the values list, followed by a description of ValueError:

{
"exception": {
"values": [
{"type": "Exception": "value": "random boring invariant was not met!"},
{"type": "ValueError", "value": "something went wrong, help!"},
]
}
}

A possible lock (java monitor object) held by this frame.

Holds information about a single stacktrace frame.

Each object should contain at least a filename, function or instruction_addr
attribute. All values are optional, but recommended.

Geographical location of the end user or device.

GPU information.

Example:

"gpu": {
"name": "AMD Radeon Pro 560",
"vendor_name": "Apple",
"memory_size": 4096,
"api_type": "Metal",
"multi_threaded_rendering": true,
"version": "Metal",
"npot_support": "Full"
}

A debug image consisting of source files for a JVM based language.

Examples:

{
"type": "jvm",
"debug_id": "395835f4-03e0-4436-80d3-136f0749a893"
}

Represents an instance of a held lock (java monitor object) in a thread.

A log entry message.

A log message is similar to the message attribute on the event itself but
can additionally hold optional parameters.

{
"message": {
"message": "My raw message with interpreted strings like %s",
"params": ["this"]
}
}

{
"message": {
"message": "My raw message with interpreted strings like {foo}",
"params": {"foo": "this"}
}
}

Mach exception information.

Optional ISO C standard error code.

A Mach Exception on Apple systems comprising a code triple and optional descriptions.

An NSError on Apple systems comprising code and signal.

Information on the POSIX signal.

Operating system or runtime meta information.

The mechanism by which an exception was generated and handled.

The exception mechanism is an optional field residing in the exception.
It carries additional information about the way the exception was created on the target system.
This includes general exception values obtained from the operating system or runtime APIs, as
well as mechanism-specific values.

Optional ISO C standard error code.

A Mach Exception on Apple systems comprising a code triple and optional descriptions.

An NSError on Apple systems comprising code and signal.

Information on the POSIX signal.

Operating system or runtime meta information to an exception mechanism.

The mechanism metadata usually carries error codes reported by the runtime or operating system,
along with a platform-dependent interpretation of these codes. SDKs can safely omit code names
and descriptions for well-known error codes, as it will be filled out by Sentry. For
proprietary or vendor-specific error codes, adding these values will give additional
information to the user.

A generic (new-style) native platform debug information file.

The type key must be one of: