- Filebeat Reference: other versions:
- Overview
- Getting Started With Filebeat
- Step 1: Installing Filebeat
- Step 2: Configuring Filebeat
- Step 3: Configuring Filebeat to Use Logstash
- Step 4: Loading the Index Template in Elasticsearch
- Step 5: Starting Filebeat
- Step 6: Loading the Kibana Index Pattern
- Quick Start for Common Log Formats
- Command Line Options
- Directory Layout
- Repositories for APT and YUM
- Running Filebeat on Docker
- Upgrading Filebeat
- How Filebeat Works
- Configuring Filebeat
- Modules
- Exported Fields
- Securing Filebeat
- Troubleshooting
- Migrating from Logstash Forwarder to Filebeat
WARNING: Version 5.6 of Filebeat has passed its EOL date.
This documentation is no longer being maintained and may be removed. If you are running this version, we strongly advise you to upgrade. For the latest information, see the current release documentation.
Debugging
editDebugging
editBy default, Filebeat sends all its output to syslog. When you run Filebeat in
the foreground, you can use the -e
command line flag to redirect the output to
standard error instead. For example:
filebeat -e
The default configuration file is filebeat.yml (the location of the file varies by
platform). You can use a different configuration file by specifying the -c
flag. For example:
filebeat -e -c myfilebeatconfig.yml
You can increase the verbosity of debug messages by enabling one or more debug
selectors. For example, to view the published transactions, you can start Filebeat
with the publish
selector like this:
filebeat -e -d "publish"
If you want all the debugging output (fair warning, it’s quite a lot), you can
use *
, like this:
filebeat -e -d "*"