# Exiting: Index management requested but the Elasticsearch output is not configured/enabled

**URL:** <https://discuss.elastic.co/t/exiting-index-management-requested-but-the-elasticsearch-output-is-not-configured-enabled/290684>\
**Category:** Beats\
**Tags:** filebeat\
**Created:** [December 1, 2021, 3:29pm UTC](https://discuss.elastic.co/t/exiting-index-management-requested-but-the-elasticsearch-output-is-not-configured-enabled/290684 "2021-12-01T15:29:29Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![cjcenizal](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/cjcenizal/32/11216_2.png) [@cjcenizal](https://discuss.elastic.co/u/cjcenizal)\
**Post date:** [December 1, 2021, 11:20pm UTC](https://discuss.elastic.co/t/exiting-index-management-requested-but-the-elasticsearch-output-is-not-configured-enabled/290684/2 "2021-12-01T23:20:43Z")

</div>

Hi @adouren, I found an older Discuss thread which looks very similar to yours: [Error index management Filebeat to Logstash](https://discuss.elastic.co/t/error-index-management-filebeat-to-logstash/218849). Could you please take a look and let me know if this is the same issue? If so, then there's an issue open to fix this bug: [[Filebeat] setup check gives spurious ILM error · Issue #16336 · elastic/beats · GitHub](https://github.com/elastic/beats/issues/16336)

Thanks!

---

_[View the full topic](https://discuss.elastic.co/t/exiting-index-management-requested-but-the-elasticsearch-output-is-not-configured-enabled/290684)._