# No filebeat index in Elasticsearch after running setup

**URL:** <https://discuss.elastic.co/t/no-filebeat-index-in-elasticsearch-after-running-setup/249017>\
**Category:** Beats\
**Tags:** filebeat\
**Created:** [September 17, 2020, 5:51pm UTC](https://discuss.elastic.co/t/no-filebeat-index-in-elasticsearch-after-running-setup/249017 "2020-09-17T17:51:49Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![stor314](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/stor314/32/74840_2.png) [@stor314](https://discuss.elastic.co/u/stor314)\
**Post date:** [September 17, 2020, 5:51pm UTC](https://discuss.elastic.co/t/no-filebeat-index-in-elasticsearch-after-running-setup/249017/1 "2020-09-17T17:51:49Z")

</div>

New to filebeat, trying to get an index up and running in elasticsearch.

I followed this guide: [https://www.elastic.co/guide/en/beats/filebeat/current/filebeat-installation-configuration.html](https://www.elastic.co/guide/en/beats/filebeat/current/filebeat-installation-configuration.html) but for some reason even after I run `filebeat setup -e` and start the Filebeat service there is no Filebeat index created in elasticsearch.

This is all on my local machine, filebeat.yml looks like the following:

```
filebeat.inputs:
- type: log
  paths:
    - C:/elk/logs/filebeatlog.log

output.elasticsearch:
  hosts: ["localhost:9200"]

```

Everything else is default.  
in the log that I'm inputting there's only one line right now, something like

2020-09-14 13:19:35,067 INFO com.class.java.blahblah.blah [main] Text Text text

Didn't do any parsing on it or anything yet, is that my problem? Or is there certain priviledges I have to give filebeat like stated in this article: [https://www.elastic.co/guide/en/beats/filebeat/master/privileges-to-publish-events.html](https://www.elastic.co/guide/en/beats/filebeat/master/privileges-to-publish-events.html) ?

I'm really lost, I've had other indices created in ElasticSearch before from Logstash so I'm not sure if its an ES problem or not.

Any help is appreciated, I am a real newbie to all this stuff. Thanks.

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [September 17, 2020, 10:12pm UTC](https://discuss.elastic.co/t/no-filebeat-index-in-elasticsearch-after-running-setup/249017/2 "2020-09-17T22:12:45Z")

</div>

What do the Filebeat logs show?

---

<div class="post-metadata">

**Author:** ![shaunak](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/shaunak/32/6643_2.png) [@shaunak](https://discuss.elastic.co/u/shaunak)\
**Post date:** [September 17, 2020, 10:21pm UTC](https://discuss.elastic.co/t/no-filebeat-index-in-elasticsearch-after-running-setup/249017/3 "2020-09-17T22:21:26Z")

</div>

Yes, please post the Filebeat logs from start up through the first 10 seconds or so. It might help to run Filebeat with `logging.level: debug` set in your `filebeat.yml` so we can see debug-level logs.

> [@stor314](#):
>
> in the log that I'm inputting there's only one line right now, something like
> 
> 2020-09-14 13:19:35,067 INFO com.class.java.blahblah.blah [main] Text Text text

You can also try to temporarily use [`output.console`](https://www.elastic.co/guide/en/beats/filebeat/current/console-output.html) instead of `output.elasticsearch` to check if Filebeat is ingesting your logs and the problem is somewhere between Filebeat and Elasticsearch or with indexing your logs as documents into Elasticsearch.

---

<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:** [October 16, 2020, 12:21am UTC](https://discuss.elastic.co/t/no-filebeat-index-in-elasticsearch-after-running-setup/249017/4 "2020-10-16T00:21:32Z")

</div>

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