# Do we need to create new index for file beat?

**URL:** https://discuss.elastic.co/t/do-we-need-to-create-new-index-for-file-beat/55663
**Category:** Beats
**Created:** [July 15, 2016, 10:49pm UTC](https://discuss.elastic.co/t/do-we-need-to-create-new-index-for-file-beat/55663 "2016-07-15T22:49:44Z")
**Posts on this page:** 3
**Page:** 1

<div class="post-metadata">

### Author: ![dubul](https://avatars.discourse-cdn.com/v4/letter/d/9f8e36/32.png) [@dubul](https://discuss.elastic.co/u/dubul)
#### Post date: [July 15, 2016, 10:49pm UTC](https://discuss.elastic.co/t/do-we-need-to-create-new-index-for-file-beat/55663/1 "2016-07-15T22:49:44Z")

</div>

I'm using filebeat to ship logs from windows machine to Elasticsearch, with default filebeats setting.  
When i try to ship logs using filebeat from other server, i couldnt see any logs on elasticsearch.

In the earlier filebeat shipping the index formed is filebeat, i want to change the name of the index jenkins logs to it if it works, i tried using editing filebeat.yml.

Does elasticsearch listen to multiple filebeat from different servers??

---

<div class="post-metadata">

### Author: ![steffens](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/steffens/32/79630_2.png) [@steffens](https://discuss.elastic.co/u/steffens)
#### Post date: [July 20, 2016, 1:44pm UTC](https://discuss.elastic.co/t/do-we-need-to-create-new-index-for-file-beat/55663/2 "2016-07-20T13:44:30Z")

</div>

Have you checked filebeat logs about output errors? filebeat normally creates index `filebeat-<event timestamp>`. If clock is not in sync (check `$ date` output), events might end up in an old index.

---

<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: [July 5, 2017, 9:50pm UTC](https://discuss.elastic.co/t/do-we-need-to-create-new-index-for-file-beat/55663/3 "2017-07-05T21:50:55Z")

</div>


