- Filebeat Reference: other versions:
- Overview
- Contributing to Beats
- 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 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
- Set up prospectors
- Manage multiline messages
- Specify general settings
- Load external configuration files
- Configure the internal queue
- Configure the output
- Load balance the output hosts
- Specify SSL settings
- Filter and enhance the exported data
- Parse logs by using ingest node
- Set up project paths
- Set up the Kibana endpoint
- Load the Kibana dashboards
- Load the Elasticsearch index template
- Set up logging
- Use environment variables in the configuration
- Autodiscover
- YAML tips and gotchas
- Regular expression support
- filebeat.reference.yml
- Modules
- Exported fields
- Securing Filebeat
- Troubleshooting
- Migrating from Logstash Forwarder to Filebeat
WARNING: Version 6.1 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.
Debug
editDebug
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 "*"