- Winlogbeat Reference: other versions:
- Overview
- Getting Started With Winlogbeat
- Setting up and running Winlogbeat
- Upgrading Winlogbeat
- Configuring Winlogbeat
- Set up Winlogbeat
- Specify general settings
- Configure the internal queue
- Configure the output
- Set up index lifecycle management
- Specify SSL settings
- Filter and Enhance the exported data
- Parse data by using ingest node
- Enrich events with geoIP information
- Set up project paths
- Set up the Kibana endpoint
- Load the Kibana dashboards
- Load the Elasticsearch index template
- Configure logging
- Use environment variables in the configuration
- YAML tips and gotchas
- HTTP Endpoint
- winlogbeat.reference.yml
- Exported fields
- Monitoring Winlogbeat
- Securing Winlogbeat
- Troubleshooting
- Contributing to Beats
NOTE: You are looking at documentation for an older release. For the latest information, see the current release documentation.
Debug
editDebug
editBy default, Winlogbeat sends all its output to syslog. When you run Winlogbeat in
the foreground, you can use the -e
command line flag to redirect the output to
standard error instead. For example:
winlogbeat -e
The default configuration file is winlogbeat.yml (the location of the file varies by
platform). You can use a different configuration file by specifying the -c
flag. For example:
winlogbeat -e -c mywinlogbeatconfig.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 Winlogbeat
with the publish
selector like this:
winlogbeat -e -d "publish"
If you want all the debugging output (fair warning, it’s quite a lot), you can
use *
, like this:
winlogbeat -e -d "*"