- Packetbeat Reference: other versions:
- Packetbeat overview
- Quick start: installation and configuration
- Set up and run
- Upgrade Packetbeat
- Configure
- Traffic sniffing
- Network flows
- Protocols
- Processes
- General settings
- Project paths
- Output
- Kerberos
- SSL
- Index lifecycle management (ILM)
- Elasticsearch index template
- Kibana endpoint
- Kibana dashboards
- Processors
- Define processors
- add_cloud_metadata
- add_cloudfoundry_metadata
- add_docker_metadata
- add_fields
- add_host_metadata
- add_id
- add_kubernetes_metadata
- add_labels
- add_locale
- add_network_direction
- add_nomad_metadata
- add_observer_metadata
- add_process_metadata
- add_tags
- append
- community_id
- convert
- copy_fields
- decode_base64_field
- decode_duration
- decode_json_fields
- decode_xml
- decode_xml_wineventlog
- decompress_gzip_field
- detect_mime_type
- dissect
- dns
- drop_event
- drop_fields
- extract_array
- fingerprint
- include_fields
- move_fields
- rate_limit
- registered_domain
- rename
- replace
- syslog
- translate_sid
- truncate_fields
- urldecode
- Internal queue
- Logging
- HTTP endpoint
- Instrumentation
- Feature flags
- packetbeat.reference.yml
- How to guides
- Exported fields
- AMQP fields
- Beat fields
- Cassandra fields
- Cloud provider metadata fields
- Common fields
- DHCPv4 fields
- DNS fields
- Docker fields
- ECS fields
- Flow Event fields
- Host fields
- HTTP fields
- ICMP fields
- Jolokia Discovery autodiscover provider fields
- Kubernetes fields
- Memcache fields
- MongoDb fields
- MySQL fields
- NFS fields
- PostgreSQL fields
- Process fields
- Raw fields
- Redis fields
- SIP fields
- Thrift-RPC fields
- Detailed TLS fields
- Transaction Event fields
- Measurements (Transactions) fields
- Monitor
- Secure
- Visualize Packetbeat data in Kibana
- Troubleshoot
- Get help
- Debug
- Understand logged metrics
- Record a trace
- Common problems
- Dashboard in Kibana is breaking up data fields incorrectly
- Packetbeat doesn’t see any packets when using mirror ports
- Packetbeat can’t capture traffic from Windows loopback interface
- Packetbeat is missing long running transactions
- Packetbeat isn’t capturing MySQL performance data
- Packetbeat uses too much bandwidth
- Error loading config file
- Found unexpected or unknown characters
- Logstash connection doesn’t work
- Publishing to Logstash fails with "connection reset by peer" message
- @metadata is missing in Logstash
- Not sure whether to use Logstash or Beats
- SSL client fails to connect to Logstash
- Monitoring UI shows fewer Beats than expected
- Dashboard could not locate the index-pattern
- High RSS memory usage due to MADV settings
- Fields show up as nested JSON in Kibana
- Contribute to Beats
Protocol-Specific Metrics
editProtocol-Specific Metrics
editPacketbeat exposes per-protocol metrics under the HTTP monitoring endpoint.
These metrics are exposed under the /inputs/ path. They can be used to
observe the activity of Packetbeat for the monitored protocol.
AF_PACKET Metrics
edit| Metric | Description |
|---|---|
|
Name of the device being monitored. |
|
Number of packets delivered by the kernel to the shared buffer. |
|
Number of packets dropped by the kernel on the socket. |
|
Number of kernel queue freezes on the socket. |
|
Number of packets handled by Packetbeat. |
|
Number of blocking syscalls made waiting for packets. |
TCP Metrics
edit| Metric | Description |
|---|---|
|
Name of the device being monitored. |
|
Number of packets processed. |
|
Number of bytes processed. |
|
Number of packets shrunk due to overlap. |
|
Number of packets dropped because of gaps. |
|
Histogram of the elapsed time between packet arrivals. |
|
Histogram of the elapsed time between packet receipt and publication. |
|
Number of TCP FIN (finish) flags observed. |
|
Number of TCP SYN (synchronization) flags observed. |
|
Number of TCP RST (reset) flags observed. |
|
Number of TCP PSH (push) flags observed. |
|
Number of TCP ACK (acknowledgement) flags observed. |
|
Number of TCP URG (urgent) flags observed. |
|
Number of TCP ECE (ECN echo) flags observed. |
|
Number of TCP CWR (congestion window reduced) flags observed. |
|
Number of TCP NS (nonce sum) flags observed. |
|
Number of headers observed, including unprocessed packets. |
UDP Metrics
edit| Metric | Description |
|---|---|
|
Name of the device being monitored. |
|
Number of packets processed. |
|
Number of bytes processed. |
|
Histogram of the elapsed time between packet arrivals. |
|
Histogram of the elapsed time between packet receipt and publication. |
On this page