# Ingest log in specific index

**URL:** <https://discuss.elastic.co/t/ingest-log-in-specific-index/347571>\
**Category:** Beats\
**Tags:** filebeat\
**Created:** [November 21, 2023, 3:08am UTC](https://discuss.elastic.co/t/ingest-log-in-specific-index/347571 "2023-11-21T03:08:29Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![stephenb](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/stephenb/32/40856_2.png) [@stephenb](https://discuss.elastic.co/u/stephenb)\
**Post date:** [November 21, 2023, 6:18am UTC](https://discuss.elastic.co/t/ingest-log-in-specific-index/347571/2 "2023-11-21T06:18:09Z")

</div>

Perhaps take a look at

> [@Filebeat writing to its own index](https://discuss.elastic.co/t/filebeat-writing-to-its-own-index/310842/28):
>
> As explained in the post I linked, You have a moduled enabled in your configuration whether it is important now or not... It overrides the output settings in some cases but let's put that aside there are other issues... Also from the docs [here](https://www.elastic.co/guide/en/beats/filebeat/7.12/elasticsearch-output.html#index-option-es)... which is your key issue... When [index lifecycle management (ILM)](https://www.elastic.co/guide/en/beats/filebeat/7.12/ilm.html) is enabled, the default index is "filebeat-%{[agent.version]}-%{+yyyy.MM.dd}-%{index\_num}" , for example, "filebeat-7.12.1-2022-07-28-000001" . Custom index settings are ignored when…

---

_[View the full topic](https://discuss.elastic.co/t/ingest-log-in-specific-index/347571)._