- Packetbeat Reference: other versions:
- Overview
- Getting Started With Packetbeat
- Upgrading Packetbeat
- Configuring Packetbeat
- Configuration Options (Reference)
- Network Device Configuration
- Flows Configuration
- Transaction Protocols Configuration
- Monitored Processes Configuration
- General Configuration
- Elasticsearch Output Configuration
- Logstash Output Configuration
- Kafka Output Configuration
- Redis Output Configuration
- File Output Configuration
- Console Output Configuration
- SSL Configuration
- Paths Configuration
- Logging Configuration
- Run Options Configuration
- Processors
- Filtering and Enhancing the Exported Data
- Configuring Packetbeat to Use Ingest Node
- Exporting GeoIP Information
- Configuring Packetbeat to Use Logstash
- Using Environment Variables in the Configuration
- Setting Traffic Capturing Options
- Configuring Thrift-RPC Support
- Maintaining the Real-Time State of the Network Topology
- YAML Tips and Gotchas
- Configuration Options (Reference)
- Exported Fields
- AMQP Fields
- Beat Fields
- Cassandra Fields
- Cloud Provider Metadata Fields
- Common Fields
- DNS Fields
- Flow Event Fields
- HTTP Fields
- ICMP Fields
- Memcache Fields
- MongoDb Fields
- MySQL Fields
- NFS Fields
- PostgreSQL Fields
- Raw Fields
- Redis Fields
- Thrift-RPC Fields
- Transaction Event Fields
- Measurements (Transactions) Fields
- Securing Packetbeat
- Visualizing Packetbeat Data in Kibana
- Troubleshooting
- Developer Guide: Adding a New Protocol
WARNING: Version 5.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.
Measurements (Transactions) Fields
editMeasurements (Transactions) Fields
editThese fields contain measurements related to the transaction.
responsetime
edittype: long
The wall clock time it took to complete the transaction. The precision is in milliseconds.
cpu_time
edittype: long
The CPU time it took to complete the transaction.
bytes_in
edittype: 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
edittype: 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
edittype: 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
edittype: long
The time it takes for the TCP connection to be established for the given transaction. The precision is in microseconds.
loadtime
edittype: 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
edittype: 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.