- Filebeat Reference: other versions:
- Filebeat overview
- Quick start: installation and configuration
- Set up and run
- Upgrade
- How Filebeat works
- Configure
- Inputs
- Modules
- General settings
- Project paths
- Config file loading
- 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_observer_metadata
- add_process_metadata
- add_tags
- community_id
- convert
- copy_fields
- decode_base64_field
- decode_cef
- decode_csv_fields
- decode_json_fields
- decompress_gzip_field
- detect_mime_type
- dissect
- dns
- drop_event
- drop_fields
- extract_array
- fingerprint
- include_fields
- rate_limit
- registered_domain
- rename
- script
- timestamp
- translate_sid
- truncate_fields
- urldecode
- Autodiscover
- Internal queue
- Load balancing
- Logging
- HTTP endpoint
- Regular expression support
- Instrumentation
- filebeat.reference.yml
- How to guides
- Override configuration settings
- Load the Elasticsearch index template
- Change the index name
- Load Kibana dashboards
- Load ingest pipelines
- Enrich events with geoIP information
- Deduplicate data
- Parse data by using ingest node
- Use environment variables in the configuration
- Avoid YAML formatting problems
- Beats central management
- Modules
- Modules overview
- ActiveMQ module
- Apache module
- Auditd module
- AWS module
- Azure module
- Barracuda module
- Bluecoat module
- CEF module
- Check Point module
- Cisco module
- CoreDNS module
- Crowdstrike module
- Cyberark module
- Cylance module
- Elasticsearch module
- Envoyproxy Module
- F5 module
- Fortinet module
- Google Cloud module
- Google Workspace module
- GSuite module
- haproxy module
- IBM MQ module
- Icinga module
- IIS module
- Imperva module
- Infoblox module
- Iptables module
- Juniper module
- Kafka module
- Kibana module
- Logstash module
- Microsoft module
- MISP module
- MongoDB module
- MSSQL module
- MySQL module
- MySQL Enterprise module
- nats module
- NetFlow module
- Netscout module
- Nginx module
- Office 365 module
- Okta module
- Oracle module
- Osquery module
- Palo Alto Networks module
- PostgreSQL module
- Proofpoint module
- RabbitMQ module
- Radware module
- Redis module
- Santa module
- Snort module
- Snyk module
- Sonicwall module
- Sophos module
- Squid module
- Suricata module
- System module
- Tomcat module
- Traefik module
- Zeek (Bro) Module
- Zoom module
- Zscaler module
- Exported fields
- ActiveMQ fields
- Apache fields
- Auditd fields
- AWS fields
- aws-cloudwatch fields
- Azure fields
- Barracuda Web Application Firewall fields
- Beat fields
- Blue Coat Director fields
- Decode CEF processor fields fields
- CEF fields
- Checkpoint fields
- Cisco fields
- Cloud provider metadata fields
- Coredns fields
- Crowdstrike fields
- Cyber-Ark fields
- CylanceProtect fields
- Docker fields
- ECS fields
- Elasticsearch fields
- Envoyproxy fields
- Big-IP Access Policy Manager fields
- Fortinet fields
- Google Cloud Platform (GCP) fields
- google_workspace fields
- gsuite fields
- HAProxy fields
- Host fields
- ibmmq fields
- Icinga fields
- IIS fields
- Imperva SecureSphere fields
- Infoblox NIOS fields
- iptables fields
- Jolokia Discovery autodiscover provider fields
- Juniper JUNOS fields
- Kafka fields
- kibana fields
- Kubernetes fields
- Log file content fields
- logstash fields
- Microsoft fields
- MISP fields
- mongodb fields
- mssql fields
- MySQL fields
- MySQL Enterprise fields
- NATS fields
- NetFlow fields
- Arbor Peakflow SP fields
- Nginx fields
- Office 365 fields
- Okta fields
- Oracle fields
- Osquery fields
- panw fields
- PostgreSQL fields
- Process fields
- Proofpoint Email Security fields
- RabbitMQ fields
- Radware DefensePro fields
- Redis fields
- s3 fields
- Google Santa fields
- Snort/Sourcefire fields
- Snyk fields
- Sonicwall-FW fields
- sophos fields
- Squid fields
- Suricata fields
- System fields
- Apache Tomcat fields
- Traefik fields
- Zeek fields
- Zoom fields
- Zscaler NSS fields
- Monitor
- Secure
- Troubleshoot
- Get help
- Debug
- Common problems
- Can’t read log files from network volumes
- Filebeat isn’t collecting lines from a file
- Too many open file handlers
- Registry file is too large
- Inode reuse causes Filebeat to skip lines
- Log rotation results in lost or duplicate events
- Open file handlers cause issues with Windows file rotation
- Filebeat is using too much CPU
- Dashboard in Kibana is breaking up data fields incorrectly
- Fields are not indexed or usable in Kibana visualizations
- Filebeat isn’t shipping the last line of a file
- Filebeat keeps open file handlers of deleted files for a long time
- Filebeat 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
- Contribute to Beats
Nginx fields
editNginx fields
editModule for parsing the Nginx log files.
nginx
editFields from the Nginx log files.
access
editContains fields for the Nginx access logs.
-
nginx.access.remote_ip_list
-
An array of remote IP addresses. It is a list because it is common to include, besides the client IP address, IP addresses from headers like
X-Forwarded-For
. Real source IP is restored tosource.ip
.type: array
-
nginx.access.body_sent.bytes
-
type: alias
alias to: http.response.body.bytes
-
nginx.access.user_name
-
type: alias
alias to: user.name
-
nginx.access.method
-
type: alias
alias to: http.request.method
-
nginx.access.url
-
type: alias
alias to: url.original
-
nginx.access.http_version
-
type: alias
alias to: http.version
-
nginx.access.response_code
-
type: alias
alias to: http.response.status_code
-
nginx.access.referrer
-
type: alias
alias to: http.request.referrer
-
nginx.access.agent
-
type: alias
alias to: user_agent.original
-
nginx.access.user_agent.device
-
type: alias
alias to: user_agent.device.name
-
nginx.access.user_agent.name
-
type: alias
alias to: user_agent.name
-
nginx.access.user_agent.os
-
type: alias
alias to: user_agent.os.full_name
-
nginx.access.user_agent.os_name
-
type: alias
alias to: user_agent.os.name
-
nginx.access.user_agent.original
-
type: alias
alias to: user_agent.original
-
nginx.access.geoip.continent_name
-
type: alias
alias to: source.geo.continent_name
-
nginx.access.geoip.country_iso_code
-
type: alias
alias to: source.geo.country_iso_code
-
nginx.access.geoip.location
-
type: alias
alias to: source.geo.location
-
nginx.access.geoip.region_name
-
type: alias
alias to: source.geo.region_name
-
nginx.access.geoip.city_name
-
type: alias
alias to: source.geo.city_name
-
nginx.access.geoip.region_iso_code
-
type: alias
alias to: source.geo.region_iso_code
error
editContains fields for the Nginx error logs.
-
nginx.error.connection_id
-
Connection identifier.
type: long
-
nginx.error.level
-
type: alias
alias to: log.level
-
nginx.error.pid
-
type: alias
alias to: process.pid
-
nginx.error.tid
-
type: alias
alias to: process.thread.id
-
nginx.error.message
-
type: alias
alias to: message
ingress_controller
editContains fields for the Ingress Nginx controller access logs.
-
nginx.ingress_controller.remote_ip_list
-
An array of remote IP addresses. It is a list because it is common to include, besides the client IP address, IP addresses from headers like
X-Forwarded-For
. Real source IP is restored tosource.ip
.type: array
-
nginx.ingress_controller.upstream_address_list
-
An array of the upstream addresses. It is a list because it is common that several upstream servers were contacted during request processing.
type: keyword
-
nginx.ingress_controller.upstream.response.length_list
-
An array of upstream response lengths. It is a list because it is common that several upstream servers were contacted during request processing.
type: keyword
-
nginx.ingress_controller.upstream.response.time_list
-
An array of upstream response durations. It is a list because it is common that several upstream servers were contacted during request processing.
type: keyword
-
nginx.ingress_controller.upstream.response.status_code_list
-
An array of upstream response status codes. It is a list because it is common that several upstream servers were contacted during request processing.
type: keyword
-
nginx.ingress_controller.http.request.length
-
The request length (including request line, header, and request body)
type: long
format: bytes
-
nginx.ingress_controller.http.request.time
-
Time elapsed since the first bytes were read from the client
type: double
format: duration
-
nginx.ingress_controller.upstream.name
-
The name of the upstream.
type: keyword
-
nginx.ingress_controller.upstream.alternative_name
-
The name of the alternative upstream.
type: keyword
-
nginx.ingress_controller.upstream.response.length
-
The length of the response obtained from the upstream server. If several servers were contacted during request process, the summary of the multiple response lengths is stored.
type: long
format: bytes
-
nginx.ingress_controller.upstream.response.time
-
The time spent on receiving the response from the upstream as seconds with millisecond resolution. If several servers were contacted during request process, the summary of the multiple response times is stored.
type: double
format: duration
-
nginx.ingress_controller.upstream.response.status_code
-
The status code of the response obtained from the upstream server. If several servers were contacted during request process, only the status code of the response from the last one is stored in this field.
type: long
-
nginx.ingress_controller.upstream.ip
-
The IP address of the upstream server. If several servers were contacted during request process, only the last one is stored in this field.
type: ip
-
nginx.ingress_controller.upstream.port
-
The port of the upstream server. If several servers were contacted during request process, only the last one is stored in this field.
type: long
-
nginx.ingress_controller.http.request.id
-
The randomly generated ID of the request
type: keyword
-
nginx.ingress_controller.body_sent.bytes
-
type: alias
alias to: http.response.body.bytes
-
nginx.ingress_controller.user_name
-
type: alias
alias to: user.name
-
nginx.ingress_controller.method
-
type: alias
alias to: http.request.method
-
nginx.ingress_controller.url
-
type: alias
alias to: url.original
-
nginx.ingress_controller.http_version
-
type: alias
alias to: http.version
-
nginx.ingress_controller.response_code
-
type: alias
alias to: http.response.status_code
-
nginx.ingress_controller.referrer
-
type: alias
alias to: http.request.referrer
-
nginx.ingress_controller.agent
-
type: alias
alias to: user_agent.original
-
nginx.ingress_controller.user_agent.device
-
type: alias
alias to: user_agent.device.name
-
nginx.ingress_controller.user_agent.name
-
type: alias
alias to: user_agent.name
-
nginx.ingress_controller.user_agent.os
-
type: alias
alias to: user_agent.os.full_name
-
nginx.ingress_controller.user_agent.os_name
-
type: alias
alias to: user_agent.os.name
-
nginx.ingress_controller.user_agent.original
-
type: alias
alias to: user_agent.original
-
nginx.ingress_controller.geoip.continent_name
-
type: alias
alias to: source.geo.continent_name
-
nginx.ingress_controller.geoip.country_iso_code
-
type: alias
alias to: source.geo.country_iso_code
-
nginx.ingress_controller.geoip.location
-
type: alias
alias to: source.geo.location
-
nginx.ingress_controller.geoip.region_name
-
type: alias
alias to: source.geo.region_name
-
nginx.ingress_controller.geoip.city_name
-
type: alias
alias to: source.geo.city_name
-
nginx.ingress_controller.geoip.region_iso_code
-
type: alias
alias to: source.geo.region_iso_code
On this page