Start Winlogbeat
Elastic Cloud Serverless projects are autoscaled environments, fully managed by Elastic and available on Elastic Cloud. Availability This functionality is generally available and ready for production usage. Serverless interfaces and procedures might differ from classic Elastic Stack deployments. The Elastic Stack includes Elastic's core products such as Elasticsearch, Kibana, Logstash, and Beats. Availability This functionality is generally available and ready for production usage. Unless stated otherwise on the page, this functionality is available when your Elastic Stack is deployed on Elastic Cloud Hosted, Elastic Cloud Enterprise, Elastic Cloud on Kubernetes, and self-managed environments. This documentation corresponds to the latest patch available for each minor version. If you're not using the latest patch, check the release notes for changes.
Serverless
Generally available
Stack
Generally available
Before starting Winlogbeat:
- Follow the steps in Quick start: installation and configuration to install, configure, and set up the Winlogbeat environment.
- Make sure Kibana and Elasticsearch are running.
- Make sure the user specified in
winlogbeat.ymlis authorized to publish events.
To start Winlogbeat, run:
PS C:\Program Files\Winlogbeat> Start-Service winlogbeat
Winlogbeat should now be running. If you used the logging configuration described here, you can view the log file at C:\Program Files\winlogbeat-Data\Logs.
By default Windows log files are stored in C:\Program Files\Winlogbeat-Data\logs.
In versions before 9.0.6, the default location for Windows log files was C:\ProgramData\winlogbeat\logs.
You can view the status of the service and control it from the Services management console in Windows. To launch the management console, run this command:
PS C:\Program Files\Winlogbeat> services.msc