This guide describes how to get started quickly with Windows log monitoring. You’ll learn how to:
- install Winlogbeat on each system you want to monitor
- specify the location of your log files
- parse log data into fields and send it to Elasticsearch
- visualize the log data in Kibana
Before you beginedit
You need Elasticsearch for storing and searching your data, and Kibana for visualizing and managing it.
Step 1: Install Winlogbeatedit
- Download the Winlogbeat zip file from the downloads page.
Extract the contents into
- Open a PowerShell prompt as an Administrator (right-click on the PowerShell icon and select Run As Administrator).
- From the PowerShell prompt, run the following commands to install the service.
PS C:\Users\Administrator> cd 'C:\Program Files\Winlogbeat' PS C:\Program Files\Winlogbeat> .\install-service-winlogbeat.ps1 Security warning Run only scripts that you trust. While scripts from the internet can be useful, this script can potentially harm your computer. If you trust this script, use the Unblock-File cmdlet to allow the script to run without this warning message. Do you want to run C:\Program Files\Winlogbeat\install-service-winlogbeat.ps1? [D] Do not run [R] Run once [S] Suspend [?] Help (default is "D"): R Status Name DisplayName ------ ---- ----------- Stopped winlogbeat winlogbeat
If script execution is disabled on your system, you need to set the
execution policy for the current session to allow the script to run. For example:
PowerShell.exe -ExecutionPolicy UnRestricted -File .\install-service-winlogbeat.ps1.
Step 2: Connect to the Elastic Stackedit
Connections to Elasticsearch and Kibana are required to set up Winlogbeat.
Set the connection information in
winlogbeat.yml. To locate this
configuration file, see Directory layout.
This examples shows a hard-coded password, but you should store sensitive values in the secrets keystore.
Set the host and port where Winlogbeat can find the Elasticsearch installation, and set the username and password of a user who is authorized to set up Winlogbeat. For example:
This example shows a hard-coded password, but you should store sensitive values in the secrets keystore.
This example shows a hard-coded fingerprint, but you should store sensitive values in the secrets keystore. The fingerprint is a HEX encoded SHA-256 of a CA certificate, when you start Elasticsearch for the first time, security features such as network encryption (TLS) for Elasticsearch are enabled by default. If you are using the self-signed certificate generated by Elasticsearch when it is started for the first time, you will need to add its fingerprint here. The fingerprint is printed on Elasticsearch start up logs, or you can refer to connect clients to Elasticsearch documentation for other options on retrieving it. If you are providing your own SSL certificate to Elasticsearch refer to Winlogbeat documentation on how to setup SSL.
If you plan to use our pre-built Kibana dashboards, configure the Kibana endpoint. Skip this step if Kibana is running on the same host as Elasticsearch.
The hostname and port of the machine where Kibana is running, for example,
mykibanahost:5601. If you specify a path after the port number, include the scheme and port:
passwordsettings for Kibana are optional. If you don’t specify credentials for Kibana, Winlogbeat uses the
passwordspecified for the Elasticsearch output.
To use the pre-built Kibana dashboards, this user must be authorized to view dashboards or have the
To learn more about required roles and privileges, see Grant users access to secured resources.
Step 3: Configure Winlogbeatedit
winlogbeat.yml, configure the event logs that you want to monitor.
winlogbeat.event_log, specify a list of event logs to monitor. By default, Winlogbeat monitors application, security, and system logs.
winlogbeat.event_logs: - name: Application - name: Security - name: System
To obtain a list of available event logs, run
Get-EventLog *in PowerShell. For more information about this command, see the configuration details for event_logs.name.
(Optional) Set logging options to write Winlogbeat logs to a file:
logging.to_files: true logging.files: path: C:\ProgramData\winlogbeat\Logs logging.level: info
After you save your configuration file, test it with the following command.
PS C:\Program Files\Winlogbeat> .\winlogbeat.exe test config -c .\winlogbeat.yml -e
For more information about configuring Winlogbeat, also see:
Step 4: Set up assetsedit
Winlogbeat comes with predefined assets for parsing, indexing, and visualizing your data. To load these assets:
Make sure the user specified in
winlogbeat.ymlis authorized to set up Winlogbeat.
From the installation directory, run:
PS > .\winlogbeat.exe setup -e
This step loads the recommended index template for writing to Elasticsearch and deploys the sample dashboards for visualizing the data in Kibana.
Step 5: Start Winlogbeatedit
Before starting Winlogbeat, modify the user credentials in
winlogbeat.yml and specify a user who is
authorized to publish events.
To start the Winlogbeat service, 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
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
Stop the Winlogbeat service with the following command:
PS C:\Program Files\Winlogbeat> Stop-Service winlogbeat
Step 6: View your data in Kibanaedit
Winlogbeat comes with pre-built Kibana dashboards and UIs for visualizing log
data. You loaded the dashboards earlier when you ran the
To open the dashboards:
In the side navigation, click Discover. To see Winlogbeat data, make sure the predefined
winlogbeat-*index pattern is selected.
If you don’t see data in Kibana, try changing the time filter to a larger range. By default, Kibana shows the last 15 minutes.
- In the side navigation, click Dashboard, then select the dashboard that you want to open.
The dashboards are provided as examples. We recommend that you customize them to meet your needs.
Now that you have your logs streaming into Elasticsearch, learn how to unify your logs, metrics, uptime, and application performance data.
Ingest data from other sources by installing and configuring other Elastic Beats:
Use the Observability apps in Kibana to search across all your data: