A transaction describes an event captured by an Elastic APM agent instrumenting a service. Some examples of a transaction might be:
- An HTTP request
- A background job
A transaction contains:
- The timestamp and duration of the event
- A unique id, type, and name
- A result (e.g. a response code)
- Some contextual data (see below for details)
It can also contain information about the authenticated
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
The agents provide some settings for users to capture customized information. This data is stored as not-indexed in a
Searchable information is stored as
Agents decide whether to sample transactions or not, and provide settings to control sampling behavior. If sampled, the spans of a transaction are sent and stored as separate documents. Within one transaction there can be several, or no spans captured.
Transactions are stored in transaction indices.