WARNING: Version 1.3 of Beats 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.
The following command line options are available for all Beats. To use these options, you need to start the Beat in the foreground. For example, the following command starts Filebeat in debugging mode:
./filebeat -c filebeat.yml -e -d "*"
For additional command line options, see the documentation for your Beat.
- Disable the publishing of events to the defined output. This option is useful only for testing the Beat.
- Pass the location of a configuration file for the Beat.
- Test the configuration file and then exit. This option is useful for troubleshooting the configuration of a Beat.
-cpuprofile <output file>
- Write CPU profile data to the specified file. This option is useful for troubleshooting the Beat.
Enable debugging for the specified selectors. For the selectors, you can specify a comma-separated
list of components, or you can use
-d "*"to enable debugging for all components. For example,
-d "publish"displays all the "publish" related messages.
- Log to stderr and disable syslog/file output.
- Start http server for profiling. This option is useful for troubleshooting and profiling the Beat.
-memprofile <output file>
- Write memory profile data to the specified output file. This option is useful for troubleshooting the Beat.
- Enable verbose output to show INFO-level messages.
- Display the Beat version and exit.