Errorsedit
An error event contains at least
information about the original exception
that occurred
or about a log
created when the exception occurred.
For simplicity, errors are represented by a unique ID.
Error data includes:
-
Both the captured
exception
and the capturedlog
of an error can contain astack trace
, which is helpful for debugging. -
The
culprit
of an error indicates where it originated. -
An error might relate to the transaction during which it happened,
via the
transaction.id
. - Some contextual data (see below).
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.