haproxy module collects and parses logs from a (
When you run the module, it performs a few tasks under the hood:
- Sets the default paths to the log files (but don’t worry, you can override the defaults)
- Makes sure each multiline log event gets sent as a single event
- Uses ingest node to parse and process the log lines, shaping the data into a structure suitable for visualizing in Kibana
- Deploys dashboards for visualizing the log data
Read the quick start to learn how to set up and run modules.
haproxy module was tested with logs from
haproxy running on AWS Linux as a gateway to a cluster of microservices.
This module is not available for Windows.
Configure the moduleedit
You can further refine the behavior of the
haproxy module by specifying
variable settings in the
modules.d/haproxy.yml file, or overriding settings at the command line.
The module is by default configured to run via syslog on port 9001. However it can also be configured to read from a file path. See the following example.
- module: haproxy log: enabled: true var.paths: ["/var/log/haproxy.log"] var.input: "file"
Each fileset has separate variable settings for configuring the behavior of the
module. If you don’t specify variable settings, the
haproxy module uses
When you specify a setting at the command line, remember to prefix the
setting with the module name, for example,
log fileset settingsedit
An array of glob-based paths that specify where to look for the log files. All
patterns supported by Go Glob
are also supported here. For example, you can use wildcards to fetch all files
from a predefined level of subdirectories:
/path/to/log/*/*.log. This fetches all
.logfiles from the subfolders of
/path/to/log. It does not fetch log files from the
/path/to/logfolder itself. If this setting is left empty, Filebeat will choose log paths based on your operating system.
This module parses logs that don’t contain timezone information. For these logs,
Filebeat reads the local timezone and uses it when parsing to convert the
timestamp to UTC. The timezone to be used for parsing is included in the event
To disable this conversion, the
event.timezone field can be removed with
If logs are originated from systems or applications with a different timezone to
the local one, the
event.timezone field can be overwritten with the original
timezone using the
See Processors for information about specifying processors in your config.
This module comes with a sample dashboard showing geolocation, distribution of requests between backends and frontends, and status codes over time. For example:
For a description of each field in the module, see the exported fields section.