- Packetbeat Reference: other versions:
- Overview
- Getting started with Packetbeat
- Setting up and running Packetbeat
- Upgrading Packetbeat
- Configuring Packetbeat
- Set traffic capturing options
- Set up flows to monitor network traffic
- Specify which transaction protocols to monitor
- Specify which processes to monitor
- Specify general settings
- Configure the internal queue
- Configure the output
- Specify SSL settings
- Filter and enhance the exported data
- Parse data by using ingest node
- Export GeoIP Information
- Set up project paths
- Set up the Kibana endpoint
- Load the Kibana dashboards
- Load the Elasticsearch index template
- Configure logging
- Use environment variables in the configuration
- YAML tips and gotchas
- HTTP Endpoint
- packetbeat.reference.yml
- Exported fields
- AMQP fields
- Beat fields
- Cassandra fields
- Cloud provider metadata fields
- Common fields
- DHCPv4 fields
- DNS fields
- Docker fields
- Flow Event fields
- Host fields
- HTTP fields
- ICMP fields
- Kubernetes fields
- Memcache fields
- MongoDb fields
- MySQL fields
- NFS fields
- PostgreSQL fields
- Raw fields
- Redis fields
- Thrift-RPC fields
- TLS fields
- Transaction Event fields
- Measurements (Transactions) fields
- Monitoring Packetbeat
- Securing Packetbeat
- Visualizing Packetbeat data in Kibana
- Troubleshooting
- Contributing to Beats
Measurements (Transactions) fields
editMeasurements (Transactions) fields
editThese 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
domContentLoadedEndanddomContentLoadedStart.