postgresql module collects and parses logs created by
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.
postgresql module was tested with logs from versions 9.5 on Ubuntu and 9.6
Configure the moduleedit
You can further refine the behavior of the
postgresql module by specifying
variable settings in the
modules.d/postgresql.yml file, or overriding settings at the command line.
The following example shows how to set paths in the
file to override the default paths for PostgreSQL logs:
- module: postgresql log: enabled: true var.paths: ["/path/to/log/postgres/*.log*"]
To specify the same settings at the command line, you use:
Each fileset has separate variable settings for configuring the behavior of the
module. If you don’t specify variable settings, the
postgresql 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 comes with two sample dashboards.
The first dashboard is for regular logs.
The second one shows the slowlogs of PostgreSQL.
For a description of each field in the module, see the exported fields section.