- Legacy APM Server Reference:
- Overview
- Installing APM Server
- Setting up and running APM Server
- Configuring APM Server
- Event Types
- Real User Monitoring (RUM)
- Tune Data Ingestion
- Storage Management
- Intake API
- Exploring data in Elasticsearch
- Exported fields
- Troubleshooting
- Release notes
APM Transaction fieldsedit
Transaction-specific data for APM
-
transaction.name
-
type: text
Generic designation of a transaction in the scope of a single service (eg. GET /users/:id).
-
transaction.name.keyword
-
type: keyword
-
transaction.type
-
type: keyword
Keyword of specific relevance in the service’s domain (eg. request, backgroundjob, etc)
duration fieldsedit
None
-
transaction.duration.us
-
type: long
format: duration
Total duration of this transaction, in microseconds.
-
transaction.result
-
type: keyword
The result of the transaction. HTTP status code for HTTP-related transactions.
-
transaction.marks
-
type: object
A user-defined mapping of groups of marks in milliseconds.
-
transaction.sampled
-
type: boolean
Transactions that are sampled will include all available information. Transactions that are not sampled will not have spans or context. Defaults to true.
-
transaction.span_count.dropped.total
-
type: long
The total amount of dropped spans for this transaction.
On this page