Errors are identified by a unique ID. An error event contains at least information about the original exception that occured or about a log created when the exception occured.

Both the captured exception and the captured log of an error can contain a stack trace, helpful for debugging.

The culprit of an error indicates where is originated.

An error might relate to the transaction during which it happened, via the transaction.id.

Errors also have some contextual data.

The contextual data describes the environment in which an event is recorded. It includes the service, the system where the service runs, and the process.

It can also contain information about the authenticated user.

An event’s context can also include information about an authenticated user, a request leading to it, or a response. For instance, HTTP requests context have url, cookies, body, headers, etc.

The agents provide some settings for users to capture customized information. This data is stored as not-indexed in a custom object. Searchable information is stored as tags instead.

Errors are stored in error indices.