WARNING: Version 1.3 of Winlogbeat 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.

« Debugging Reference »

› ›

Frequently Asked Questions

edit

Frequently Asked Questions

edit

This section contains frequently asked questions about Winlogbeat. Also check out the Winlogbeat discussion forum.

Dashboard in Kibana is breaking up data fields incorrectly?

edit

The index template might not be loaded correctly. See Step 4: Loading the Index Template in Elasticsearch.

Logstash connection doesn’t work?

edit

You may have configured Logstash or Winlogbeat incorrectly. To resolve the issue:

Make sure that Logstash is running and you can connect to it. First, try to ping the Logstash host to verify that you can reach it from the host running Winlogbeat. Then use either nc or telnet to make sure that the port is available. For example:
```
ping <hostname or IP>
telnet <hostname or IP> 5044
```
Verify that the config file for Winlogbeat specifies the correct port where Logstash is running.
Make sure that the Elasticsearch output is commented out in the config file and the Logstash output is uncommented.
Confirm that the most recent Beats input plugin for Logstash is installed and configured. Note that Beats will not connect to the Lumberjack input plugin. See Updating the Beats Input Plugin for Logstash.

@metadata is missing in Logstash?

edit

Logstash outputs remove @metadata fields automatically. Therefore, if Logstash instances are chained directly or via some message queue (for example, Redis or Kafka), the @metadata field will not be available in the final Logstash instance.

To preserve @metadata fields, use the Logstash mutate filter with the rename setting to rename the fields to non-internal fields.

Difference between Logstash and Beats?

edit

Beats are lightweight data shippers that you install as agents on your servers to send specific types of operational data to Elasticsearch. Beats have a small footprint and use fewer system resources than Logstash.

Logstash has a larger footprint, but provides a broad array of input, filter, and output plugins for collecting, enriching, and transforming data from a variety of sources.

For more information, see the Logstash Introduction and the Beats Overview.

SSL client fails to connect to Logstash?

edit

The host running Logstash might be unreachable or the certificate may not be valid. To resolve your issue:

Make sure that Logstash is running and you can connect to it. First, try to ping the Logstash host to verify that you can reach it from the host running Winlogbeat. Then use either nc or telnet to make sure that the port is available. For example:
```
ping <hostname or IP>
telnet <hostname or IP> 5044
```
Verify that the certificate is valid and that the hostname and IP match.

For testing purposes only, you can set insecure: true to disable hostname checking.
Use OpenSSL to test connectivity to the Logstash server and diagnose problems. See the OpenSSL documentation for more info.
Make sure that you have enabled SSL (set ssl => true) when configuring the Beats input plugin for Logstash.

Common SSL-Related Errors and Resolutions

edit

Here are some common errors and ways to fix them:

x509: cannot validate certificate for <IP address> because it doesn’t contain any IP SANs

edit

This happens because your certificate is only valid for the hostname present in the Subject field.

To resolve this problem, try one of these solutions:

Create a DNS entry for the hostname mapping it to the server’s IP.
Create an entry in /etc/hosts for the hostname. Or on Windows add an entry to C:\Windows\System32\drivers\etc\hosts.
Re-create the server certificate and add a SubjectAltName (SAN) for the IP address of the server. This make the server’s certificate valid for both the hostname and the IP address.

getsockopt: no route to host

edit

This is not a TLS problem. It’s a networking problem. Make sure the two hosts can communicate.

getsockopt: connection refused

edit

This is not a TLS problem. Make sure that Logstash is running and that there is no firewall blocking the traffic.

No connection could be made because the target machine actively refused it

edit

A firewall is refusing the connection. Check if a firewall is blocking the traffic on the client, the network, or the destination host.

« Debugging Reference »