- 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
- Configure index lifecycle management
- Specify SSL settings
- Filter and enhance the exported data
- Define processors
- Add cloud metadata
- Add fields
- Add labels
- Add the local time zone
- Add tags
- Decode JSON fields
- Decode Base64 fields
- Decompress gzip fields
- Community ID Network Flow Hash
- Convert
- Drop events
- Drop fields from events
- Extract array
- Keep fields from events
- Registered Domain
- Rename fields from events
- Add Kubernetes metadata
- Add Docker metadata
- Add Host metadata
- Add Observer metadata
- Dissect strings
- DNS Reverse Lookup
- Add process metadata
- Parse data by using ingest node
- Enrich events with geoIP information
- Configure project paths
- Configure 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
- 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
- Thrift-RPC fields
- TLS fields
- Transaction Event fields
- Measurements (Transactions) fields
- Monitoring Packetbeat
- Securing Packetbeat
- Visualizing Packetbeat data in Kibana
- Troubleshooting
- Get help
- Debug
- 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
- @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
- Fields show up as nested JSON in Kibana
- Contributing to Beats
DNS fields
editDNS fields
editDNS-specific event fields.
-
dns.flags.authoritative -
A DNS flag specifying that the responding server is an authority for the domain name used in the question.
type: boolean
-
dns.flags.recursion_available -
A DNS flag specifying whether recursive query support is available in the name server.
type: boolean
-
dns.flags.recursion_desired -
A DNS flag specifying that the client directs the server to pursue a query recursively. Recursive query support is optional.
type: boolean
-
dns.flags.authentic_data -
A DNS flag specifying that the recursive server considers the response authentic.
type: boolean
-
dns.flags.checking_disabled -
A DNS flag specifying that the client disables the server signature validation of the query.
type: boolean
-
dns.flags.truncated_response -
A DNS flag specifying that only the first 512 bytes of the reply were returned.
type: boolean
-
dns.question.etld_plus_one -
The effective top-level domain (eTLD) plus one more label. For example, the eTLD+1 for "foo.bar.golang.org." is "golang.org.". The data for determining the eTLD comes from an embedded copy of the data from http://publicsuffix.org.
example: amazon.co.uk.
-
dns.answers_count -
The number of resource records contained in the
dns.answersfield.type: long
-
dns.authorities -
An array containing a dictionary for each authority section from the answer.
type: object
-
dns.authorities_count -
The number of resource records contained in the
dns.authoritiesfield. Thedns.authoritiesfield may or may not be included depending on the configuration of Packetbeat.type: long
-
dns.authorities.name -
The domain name to which this resource record pertains.
example: example.com.
-
dns.authorities.type -
The type of data contained in this resource record.
example: NS
-
dns.authorities.class -
The class of DNS data contained in this resource record.
example: IN
-
dns.additionals -
An array containing a dictionary for each additional section from the answer.
type: object
-
dns.additionals_count -
The number of resource records contained in the
dns.additionalsfield. Thedns.additionalsfield may or may not be included depending on the configuration of Packetbeat.type: long
-
dns.additionals.name -
The domain name to which this resource record pertains.
example: example.com.
-
dns.additionals.type -
The type of data contained in this resource record.
example: NS
-
dns.additionals.class -
The class of DNS data contained in this resource record.
example: IN
-
dns.additionals.ttl -
The time interval in seconds that this resource record may be cached before it should be discarded. Zero values mean that the data should not be cached.
type: long
-
dns.additionals.data -
The data describing the resource. The meaning of this data depends on the type and class of the resource record.
-
dns.opt.version -
The EDNS version.
example: 0
-
dns.opt.do -
If set, the transaction uses DNSSEC.
type: boolean
-
dns.opt.ext_rcode -
Extended response code field.
example: BADVERS
-
dns.opt.udp_size -
Requestor’s UDP payload size (in bytes).
type: long