# Multiple indexes not being created for multiple log files

**URL:** <https://discuss.elastic.co/t/multiple-indexes-not-being-created-for-multiple-log-files/358817>\
**Category:** Beats\
**Tags:** filebeat\
**Created:** [May 6, 2024, 11:23am UTC](https://discuss.elastic.co/t/multiple-indexes-not-being-created-for-multiple-log-files/358817 "2024-05-06T11:23:55Z")\
**Posts on this page:** 6\
**Page:** 2

<div class="post-metadata">

**Author:** ![developer\_cloud](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/developer_cloud/32/134045_2.png) [@developer\_cloud](https://discuss.elastic.co/u/developer_cloud)\
**Post date:** [September 9, 2024, 12:31pm UTC](https://discuss.elastic.co/t/multiple-indexes-not-being-created-for-multiple-log-files/358817/23 "2024-09-09T12:31:32Z")

</div>

Hi @ashishtiwari1993, I looked through various documentations and blogs but mostly came across the idea that we can configure only 1 rollback alias for a particular ilm policy. Although when I'm trying to configure one rollback alias, I'm getting the below error:  
`Connection marked as failed because the onConnect callback failed: error creating index management handler: error creating ES handler: error unpacking lifecycle config: can not convert 'string' into 'bool' accessing 'setup.ilm.enabled'`  
The ILM configuration is as below

```auto
# ================================= ILM Configure ================================
setup.ilm.enabled: auto
setup.ilm.rollover_alias: "filebeat-log-test"
setup.ilm.pattern: "{now/d}-0001"
setup.ilm.policy_name: "filebeat-log-test-ilm-policy"
setup.ilm.check_exists: true
setup.ilm.overwrite: false

```

---

<div class="post-metadata">

**Author:** ![ashishtiwari1993](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ashishtiwari1993/32/135241_2.png) [@ashishtiwari1993](https://discuss.elastic.co/u/ashishtiwari1993)\
**Post date:** [September 10, 2024, 5:13am UTC](https://discuss.elastic.co/t/multiple-indexes-not-being-created-for-multiple-log-files/358817/24 "2024-09-10T05:13:48Z")

</div>

I am curious about `setup.ilm.enabled:auto` but as per [doc](https://www.elastic.co/guide/en/beats/filebeat/current/ilm.html#_configuration_options_31) valid values should be `true` or `false`. Could you please confirm?

---

<div class="post-metadata">

**Author:** ![developer\_cloud](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/developer_cloud/32/134045_2.png) [@developer\_cloud](https://discuss.elastic.co/u/developer_cloud)\
**Post date:** [September 10, 2024, 6:35am UTC](https://discuss.elastic.co/t/multiple-indexes-not-being-created-for-multiple-log-files/358817/25 "2024-09-10T06:35:54Z")

</div>

@ashishtiwari1993, I tried it with both. but still the same response. Could this be happening due to version differences? I've configured filebeat with version 8.x while elastic has 7.17 version.

---

<div class="post-metadata">

**Author:** ![ashishtiwari1993](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ashishtiwari1993/32/135241_2.png) [@ashishtiwari1993](https://discuss.elastic.co/u/ashishtiwari1993)\
**Post date:** [September 10, 2024, 6:40am UTC](https://discuss.elastic.co/t/multiple-indexes-not-being-created-for-multiple-log-files/358817/26 "2024-09-10T06:40:46Z")

</div>

Quite possible because in [7.17](https://www.elastic.co/guide/en/beats/filebeat/7.17/ilm.html), value values were `true`, `false` and `auto` but in [8.15](https://www.elastic.co/guide/en/beats/filebeat/8.15/ilm.html), It is just `true` and `false`.

While upgrading, I will recommend to check [breaking changes](https://www.elastic.co/guide/en/beats/libbeat/8.15/breaking-changes.html).

---

<div class="post-metadata">

**Author:** ![developer\_cloud](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/developer_cloud/32/134045_2.png) [@developer\_cloud](https://discuss.elastic.co/u/developer_cloud)\
**Post date:** [September 10, 2024, 6:43am UTC](https://discuss.elastic.co/t/multiple-indexes-not-being-created-for-multiple-log-files/358817/27 "2024-09-10T06:43:52Z")

</div>

I'm trying to create multiple indexes for n number of log file paths provided. I was initially trying to create different ILM Policy for each of those but then moved to creating a single ILM Policy and single template settings for all. However, filebeat fails at ILM Policy creation. I've utilized the `fields.log-name` parameter to get different indexes for each of the log files.

---

<div class="post-metadata">

**Author:** ![ashishtiwari1993](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ashishtiwari1993/32/135241_2.png) [@ashishtiwari1993](https://discuss.elastic.co/u/ashishtiwari1993)\
**Post date:** [September 11, 2024, 5:27am UTC](https://discuss.elastic.co/t/multiple-indexes-not-being-created-for-multiple-log-files/358817/28 "2024-09-11T05:27:34Z")

</div>

Another approach could be, You define multiple `inputs` in filebeat configuration file for different set of logs file (or individual)

[Previous page](https://discuss.elastic.co/t/multiple-indexes-not-being-created-for-multiple-log-files/358817.md?page=1)
