Unable to see filebeat in kibana

[Enzo_baker (Saravanan)]

Filebeat yml:

filebeat.inputs:

Each - is an input. Most options can be set at the input level, so

you can use different inputs for various configurations.

Below are the input specific configurations.

• type: log

  Change to true to enable this input configuration.

  enabled: true

  Paths that should be crawled and fetched. Glob based paths.

  paths:
  #- /var/log/*.log

  • D:\ELK\logs*

#==================== Elasticsearch template setting ==========================

setup.template.settings:
index.number_of_shards: 1

output.elasticsearch:

Array of hosts to connect to.

hosts: ["localhost:9200"]

Elastic indices:

health status index uuid pri rep docs.count docs.deleted store.size pri.store.size
green open .kibana_task_manager_1 RQofB4VrTG-BQohcqBKOIQ 1 0 2 1 16.2kb 16.2kb
green open .apm-agent-configuration U0fwynZRQJuQpx67lNJt-A 1 0 0 0 283b 283b
green open .kibana_1 a-j0bczeSpq58OXeGXqHWg 1 0 6 0 22.1kb 22.1kb

No filebeat* index is visible.

I am a beginner to ELK. My set up is,

Filebeat -> ElasticSearch -> Kibana

I have gone through many threads but couldnt resolve my problem.
Any advise is highly appreciated. Thanks!

[dadoonet (David Pilato)]

Welcome! I moved your question to #beats:filebeat

Please format your code, logs or configuration files using </> icon as explained in this guide and not the citation button. It will make your post more readable.

Or use markdown style like:

```
CODE
```

This is the icon to use if you are not using markdown format:

There's a live preview panel for exactly this reasons.

Lots of people read these forums, and many of them will simply skip over a post that is difficult to read, because it's just too large an investment of their time to try and follow a wall of badly formatted text.
If your goal is to get an answer to your questions, it's in your interest to make it as easy to read and understand as possible.
Please update your post.