IMPORTANT: No additional bug fixes or documentation updates will be released for this version. For the latest information, see the current release documentation.

« Transaction Event fields Monitoring Packetbeat »

› ›

Measurements (Transactions) fields

edit

Measurements (Transactions) fields

edit

These fields contain measurements related to the transaction.

responsetime

type: long

The wall clock time it took to complete the transaction. The precision is in milliseconds.

cpu_time

type: long

The CPU time it took to complete the transaction.

bytes_in

type: long

format: bytes

The number of bytes of the request. Note that this size is the application layer message length, without the length of the IP or TCP headers.

bytes_out

type: long

format: bytes

The number of bytes of the response. Note that this size is the application layer message length, without the length of the IP or TCP headers.

dnstime

type: long

The time it takes to query the name server for a given request. This is typically used for RUM (real-user-monitoring) but can also have values for server-to-server communication when DNS is used for service discovery. The precision is in microseconds.

connecttime

type: long

The time it takes for the TCP connection to be established for the given transaction. The precision is in microseconds.

loadtime

type: long

The time it takes for the content to be loaded. This is typically used for RUM (real-user-monitoring) but it can make sense in other cases as well. The precision is in microseconds.

domloadtime

type: long

In RUM (real-user-monitoring), the total time it takes for the DOM to be loaded. In terms of the W3 Navigation Timing API, this is the difference between domContentLoadedEnd and domContentLoadedStart.

« Transaction Event fields Monitoring Packetbeat »