# Winlogbeat indices works but not see in Kibana

**URL:** <https://discuss.elastic.co/t/winlogbeat-indices-works-but-not-see-in-kibana/128968>\
**Category:** Beats\
**Created:** [April 21, 2018, 12:45pm UTC](https://discuss.elastic.co/t/winlogbeat-indices-works-but-not-see-in-kibana/128968 "2018-04-21T12:45:42Z")\
**Posts on this page:** 10\
**Page:** 1

<div class="post-metadata">

**Author:** ![lcguy](https://avatars.discourse-cdn.com/v4/letter/l/35a633/32.png) [@lcguy](https://discuss.elastic.co/u/lcguy)\
**Post date:** [April 21, 2018, 12:45pm UTC](https://discuss.elastic.co/t/winlogbeat-indices-works-but-not-see-in-kibana/128968/1 "2018-04-21T12:45:42Z")

</div>

## Hi, I have ELK stack working well with Logstash. Input is Syslog. Just trying out winlogbeat in from Windows server to CentOS (ELK) server not works. Checking indices, I can see all but, unable to view in Kibana. Need help how to configure correct settings in logstash config.

Here is logstash config.

input {  
beats {  
port =\> 5443  
type =\> "log"  
}  
udp {  
port =\> 5514  
type =\> syslog  
}  
}

filter {  
if [type] == "syslog" {  
grok {  
match =\> { "message" =\> "%{SYSLOGTIMESTAMP:syslog\_timestamp} %{SYSLOGHOST:syslog\_hostname} %{DATA:syslog\_program}(?:[%{POSINT:syslog\_pid}])?: %{GREEDYDATA:syslog\_message}" }  
add\_field =\> ["received\_at", "%{@timestamp}"]  
add\_field =\> ["received\_from", "%{host}"]  
}  
date {  
match =\> ["syslog\_timestamp", "MMM d HH:mm:ss", "MMM dd HH:mm:ss"]  
}  
}  
}

output {  
elasticsearch { hosts =\> ["localhost:9200"] }  
stdout { codec =\> rubydebug }  
}  
+++++++++++++++++++++++++++++++++++++++++++++++++++  
curl -XGET "[http://localhost:9200/\_cat/indices?v](http://localhost:9200/_cat/indices?v)"  
health status index uuid pri rep docs.count docs.deleted store.size pri.store.size  
yellow open logstash-2017.12.30 y9YI3we-STKscYmYqg-XgQ 5 1 0 0 955b 955b  
red open logstash-2018.04.01 0igJRyd2Qwi8-woLr5SZ3g 5 1 580 0 2.7mb 2.7mb  
red open winlogbeat-6.2.4-2018.04.18 gUqSMxaWQO-0gG9rzp0FOQ 3 1  
yellow open winlogbeat-6.2.4-2017.12.22 0rX2D\_1sQsKNa1m78KyjPw 3 1 300 0 792.1kb 792.1kb  
yellow open .kibana cJgmLTRyTUqvJw6UzvC9Eg 1 1 3 0 52kb 52kb  
yellow open logstash-2017.12.31 HVbJaMekSF20Set0LlOa-Q 5 1 0 0 955b 955b  
red open %{[@metadata][beat]}-2018.04.21 rc2QizN9SZmPU69UVKn2tg 5 1 0 0 648b 648b  
red open logstash-2017.12.23 5E4iR04zSIqKLsaQxF6tQA 5 1 52 0 451.2kb 451.2kb  
yellow open logstash-2018.04.18 v2qTfqSKTeeS6-1nxpBW5Q 5 1 49985 0 10mb 10mb  
red open winlogbeat-6.2.4-2018.04.20 NwAEDWaPQZiyNpvkQpRfug 3 1  
red open winlogbeat-6.2.4-2018.04.19 Ug67pfGKT6GHNYdjBRUDSQ 3 1  
yellow open logstash-2018.04.21 LX\_DTsLOTU2dDpF\_oFfgtQ 5 1 98130 0 39.7mb 39.7mb  
yellow open winlogbeat-6.2.4-2018.04.01 ts6px3TiRVSdQoAqumcwJw 3 1 414 0 1.1mb 1.1mb

---

<div class="post-metadata">

**Author:** ![JKhondhu](https://avatars.discourse-cdn.com/v4/letter/j/ed655f/32.png) [@JKhondhu](https://discuss.elastic.co/u/JKhondhu)\
**Post date:** [April 21, 2018, 5:08pm UTC](https://discuss.elastic.co/t/winlogbeat-indices-works-but-not-see-in-kibana/128968/2 "2018-04-21T17:08:17Z")

</div>

Are you able to see any of that `_cat/indices` data in Kibana?

The winlogbeat-6.2.4-2018.\* indices look red, are you able to pin point why?

---

<div class="post-metadata">

**Author:** ![lcguy](https://avatars.discourse-cdn.com/v4/letter/l/35a633/32.png) [@lcguy](https://discuss.elastic.co/u/lcguy)\
**Post date:** [April 22, 2018, 12:51pm UTC](https://discuss.elastic.co/t/winlogbeat-indices-works-but-not-see-in-kibana/128968/3 "2018-04-22T12:51:15Z")

</div>

Finally, filebeat, winlogbeat and syslog are working now.  
The reason is my server's resource in test VM. After I rebuild new server with high memory it is working now.

But, there is one issue with filebeat. I send sample IIS log from Windows server to Kibana via logstash with SSL cert certificate. It failed to received log. What I can confirmed is capturing packet in CentOS (ELK) server. All packets reset.

Then, I disabled SSL in server as well as in filebeat, it works!!  
So, may I know what is the correct configuration of the filebeat configuration with SSL cert?

Here is mine.

filebeat.prospectors:

- type: log  
enabled: true  
paths:
  - C:\inetpub\logs\LogFiles\*\*  
fields:  
type: iis  
fields\_under\_root: true  
encoding: utf-8  
exclude\_lines: ["^#"]  
exclude\_files: [".zip"]  
ignore\_older: 2h  
output.logstash:  
hosts: ["192.168.1.50:5443"]  
tls:  
certificate\_authorities: ["E:/filebeat-6.2.4-windows-x86\_64/logstash-forwarder.crt"]

---

<div class="post-metadata">

**Author:** ![JKhondhu](https://avatars.discourse-cdn.com/v4/letter/j/ed655f/32.png) [@JKhondhu](https://discuss.elastic.co/u/JKhondhu)\
**Post date:** [April 23, 2018, 8:18am UTC](https://discuss.elastic.co/t/winlogbeat-indices-works-but-not-see-in-kibana/128968/4 "2018-04-23T08:18:32Z")

</div>

Hi,

Following such steps here: [https://www.elastic.co/guide/en/beats/filebeat/current/configuring-ssl-logstash.html](https://www.elastic.co/guide/en/beats/filebeat/current/configuring-ssl-logstash.html)

Let me know how far you get and what errors you see.

---

<div class="post-metadata">

**Author:** ![lcguy](https://avatars.discourse-cdn.com/v4/letter/l/35a633/32.png) [@lcguy](https://discuss.elastic.co/u/lcguy)\
**Post date:** [April 23, 2018, 11:06pm UTC](https://discuss.elastic.co/t/winlogbeat-indices-works-but-not-see-in-kibana/128968/5 "2018-04-23T23:06:27Z")

</div>

I have gone through this document. All works well except from line start with tls:

The link havent mention how to set correct path for crt file in Windows.

Thats why I am confused. Some document mentioned that it shoud start with ssl: instead of tls:

Please share with me anyone has working config file for Windows using filebeat with tls.

---

<div class="post-metadata">

**Author:** ![JKhondhu](https://avatars.discourse-cdn.com/v4/letter/j/ed655f/32.png) [@JKhondhu](https://discuss.elastic.co/u/JKhondhu)\
**Post date:** [April 24, 2018, 8:08am UTC](https://discuss.elastic.co/t/winlogbeat-indices-works-but-not-see-in-kibana/128968/6 "2018-04-24T08:08:45Z")

</div>

Which documentation did you follow to get the config you have right now? With the filebeat.prospectors paths tls?

---

<div class="post-metadata">

**Author:** ![lcguy](https://avatars.discourse-cdn.com/v4/letter/l/35a633/32.png) [@lcguy](https://discuss.elastic.co/u/lcguy)\
**Post date:** [April 24, 2018, 8:10am UTC](https://discuss.elastic.co/t/winlogbeat-indices-works-but-not-see-in-kibana/128968/7 "2018-04-24T08:10:21Z")

</div>

Yes, I tried with tls and ssl too. Both failed.  
Disabling tls or ssl works straight away.

If enable ssl or tls, server is rejecting with TCP RST packet.

Thanks.

---

<div class="post-metadata">

**Author:** ![JKhondhu](https://avatars.discourse-cdn.com/v4/letter/j/ed655f/32.png) [@JKhondhu](https://discuss.elastic.co/u/JKhondhu)\
**Post date:** [April 24, 2018, 8:27am UTC](https://discuss.elastic.co/t/winlogbeat-indices-works-but-not-see-in-kibana/128968/8 "2018-04-24T08:27:52Z")

</div>

> [@JKhondhu](#):
>
> Which documentation did you follow

...?

---

<div class="post-metadata">

**Author:** ![lcguy](https://avatars.discourse-cdn.com/v4/letter/l/35a633/32.png) [@lcguy](https://discuss.elastic.co/u/lcguy)\
**Post date:** [April 24, 2018, 8:32am UTC](https://discuss.elastic.co/t/winlogbeat-indices-works-but-not-see-in-kibana/128968/9 "2018-04-24T08:32:18Z")

</div>

This is the one.  
[https://www.elastic.co/downloads/beats/filebeat](https://www.elastic.co/downloads/beats/filebeat)

I have one CentOS and this server can send filebeat log from /var/log/ using tls with crt file.  
Only from Windows server is having issue with IIS log from C:\Inetpub\www\logs folder.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [May 22, 2018, 10:32am UTC](https://discuss.elastic.co/t/winlogbeat-indices-works-but-not-see-in-kibana/128968/10 "2018-05-22T10:32:26Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.
