- Filebeat Reference: other versions:
- Overview
- Getting Started With Filebeat
- Step 1: Install Filebeat
- Step 2: Configure Filebeat
- Step 3: Configure Filebeat to use Logstash
- Step 4: Load the index template in Elasticsearch
- Step 5: Set up the Kibana dashboards
- Step 6: Start Filebeat
- Step 7: View the sample Kibana dashboards
- Quick start: modules for common log formats
- Repositories for APT and YUM
- Setting up and running Filebeat
- Upgrading Filebeat
- How Filebeat works
- Configuring Filebeat
- Specify which modules to run
- Configure inputs
- Manage multiline messages
- Specify general settings
- Load external configuration files
- Configure the internal queue
- Configure the output
- Configure index lifecycle management
- Load balance the output hosts
- 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
- Drop events
- Drop fields from events
- Keep fields from events
- Rename fields from events
- Add Kubernetes metadata
- Add Docker metadata
- Add Host 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
- Autodiscover
- YAML tips and gotchas
- Regular expression support
- HTTP Endpoint
- filebeat.reference.yml
- Beats central management
- Modules
- Modules overview
- Apache module
- Auditd module
- Elasticsearch module
- haproxy module
- Icinga module
- IIS module
- Iptables module
- Kafka module
- Kibana module
- Logstash module
- MongoDB module
- MySQL module
- Nginx module
- Osquery module
- PostgreSQL module
- Redis module
- Santa module
- Suricata module
- System module
- Traefik module
- Zeek (Bro) Module
- Exported fields
- Apache fields
- Auditd fields
- Beat fields
- Cloud provider metadata fields
- Docker fields
- ECS fields
- elasticsearch fields
- haproxy fields
- Host fields
- Icinga fields
- IIS fields
- iptables fields
- Kafka fields
- kibana fields
- Kubernetes fields
- Log file content fields
- logstash fields
- mongodb fields
- MySQL fields
- NetFlow fields
- Nginx fields
- Osquery fields
- PostgreSQL fields
- Process fields
- Redis fields
- Google Santa fields
- Suricata fields
- System fields
- Traefik fields
- Zeek fields
- Monitoring Filebeat
- Securing Filebeat
- Troubleshooting
- Contributing to Beats
haproxy fields
edithaproxy fields
edithaproxy Module
haproxy fields
edit-
haproxy.frontend_name -
Name of the frontend (or listener) which received and processed the connection.
-
haproxy.backend_name -
Name of the backend (or listener) which was selected to manage the connection to the server.
-
haproxy.server_name -
Name of the last server to which the connection was sent.
-
haproxy.total_waiting_time_ms -
type: long
Total time in milliseconds spent waiting in the various queues
-
haproxy.connection_wait_time_ms -
type: long
Total time in milliseconds spent waiting for the connection to establish to the final server
-
haproxy.bytes_read -
type: long
Total number of bytes transmitted to the client when the log is emitted.
-
haproxy.time_queue -
type: long
Total time in milliseconds spent waiting in the various queues.
-
haproxy.time_backend_connect -
type: long
Total time in milliseconds spent waiting for the connection to establish to the final server, including retries.
-
haproxy.server_queue -
type: long
Total number of requests which were processed before this one in the server queue.
-
haproxy.backend_queue -
type: long
Total number of requests which were processed before this one in the backend’s global queue.
-
haproxy.bind_name -
Name of the listening address which received the connection.
-
haproxy.error_message -
type: text
Error message logged by HAProxy in case of error.
-
haproxy.source -
type: keyword
The HAProxy source of the log
-
haproxy.termination_state -
Condition the session was in when the session ended.
-
haproxy.mode -
type: keyword
mode that the frontend is operating (TCP or HTTP)
connections fields
editContains various counts of connections active in the process.
-
haproxy.connections.active -
type: long
Total number of concurrent connections on the process when the session was logged.
-
haproxy.connections.frontend -
type: long
Total number of concurrent connections on the frontend when the session was logged.
-
haproxy.connections.backend -
type: long
Total number of concurrent connections handled by the backend when the session was logged.
-
haproxy.connections.server -
type: long
Total number of concurrent connections still active on the server when the session was logged.
-
haproxy.connections.retries -
type: long
Number of connection retries experienced by this session when trying to connect to the server.
client fields
editInformation about the client doing the request
-
haproxy.client.ip -
type: alias
alias to: source.address
-
haproxy.client.port -
type: alias
alias to: source.port
-
haproxy.process_name -
type: alias
alias to: process.name
-
haproxy.pid -
type: alias
alias to: process.pid
destination fields
editDestination information
-
haproxy.destination.port -
type: alias
alias to: destination.port
-
haproxy.destination.ip -
type: alias
alias to: destination.ip
geoip fields
editContains GeoIP information gathered based on the client.ip field. Only present if the GeoIP Elasticsearch plugin is available and used.
-
haproxy.geoip.continent_name -
type: alias
alias to: source.geo.continent_name
-
haproxy.geoip.country_iso_code -
type: alias
alias to: source.geo.country_iso_code
-
haproxy.geoip.location -
type: alias
alias to: source.geo.location
-
haproxy.geoip.region_name -
type: alias
alias to: source.geo.region_name
-
haproxy.geoip.city_name -
type: alias
alias to: source.geo.city_name
-
haproxy.geoip.region_iso_code -
type: alias
alias to: source.geo.region_iso_code
http fields
editPlease add description
response fields
editFields related to the HTTP response
-
haproxy.http.response.captured_cookie -
Optional "name=value" entry indicating that the client had this cookie in the response.
-
haproxy.http.response.captured_headers -
type: keyword
List of headers captured in the response due to the presence of the "capture response header" statement in the frontend.
-
haproxy.http.response.status_code -
type: alias
alias to: http.response.status_code
request fields
editFields related to the HTTP request
-
haproxy.http.request.captured_cookie -
Optional "name=value" entry indicating that the server has returned a cookie with its request.
-
haproxy.http.request.captured_headers -
type: keyword
List of headers captured in the request due to the presence of the "capture request header" statement in the frontend.
-
haproxy.http.request.raw_request_line -
type: keyword
Complete HTTP request line, including the method, request and HTTP version string.
-
haproxy.http.request.time_wait_without_data_ms -
type: long
Total time in milliseconds spent waiting for the server to send a full HTTP response, not counting data.
-
haproxy.http.request.time_wait_ms -
type: long
Total time in milliseconds spent waiting for a full HTTP request from the client (not counting body) after the first byte was received.
tcp fields
editTCP log format
-
haproxy.tcp.connection_waiting_time_ms -
type: long
Total time in milliseconds elapsed between the accept and the last close
On this page