WARNING: Version 6.2 of Packetbeat has passed its EOL date.

This documentation is no longer being maintained and may be removed. If you are running this version, we strongly advise you to upgrade. 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`

edit

type: long

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

`cpu_time`

edit

type: long

The CPU time it took to complete the transaction.

`bytes_in`

edit

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`

edit

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`

edit

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`

edit

type: long

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

`loadtime`

edit

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`

edit

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 »