# 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:** 4\
**Page:** 1

<div class="post-metadata">

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

</div>

Hi,

I configured filebeat.yml with logstash output but I got this error: Exiting: Index management requested but the Elasticsearch output is not configured/enabled

filebeat.yml

```auto
filebeat.config:
  modules:
    path: ${path.config}/modules.d/*.yml
    reload.enabled: false

processors:
- add_cloud_metadata: ~

output.logstash:
  hosts: ["10.21.2.237:5044", "10.21.2.226:5044"]
  loadbalance: true

```

modules.d/apache.yml

```auto
- module: apache
  access:
    enabled: true
    var.paths: ["/usr/share/filebeat/logs/access.log*"]
  error:
    enabled: true
    var.paths: ["/usr/share/filebeat/logs/error.log*"]

```

logstahs.pipeline:

```auto
input {
        beats {
                port => 5044
        }

        tcp {
                port => 5000
        }
}

## Add your filters / logstash plugins configuration here

output {
        elasticsearch {
                hosts => "elasticsearch:9200"
                user => "elastic"
                password => "changeme"
                ecs_compatibility => disabled
        }
}

```

i want filebeat.yml send to logstash on port 5044.

best regard

Olivier

---

<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!

---

<div class="post-metadata">

**Author:** ![adouren](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/adouren/32/96766_2.png) [@adouren](https://discuss.elastic.co/u/adouren)\
**Post date:** [December 2, 2021, 8:41am UTC](https://discuss.elastic.co/t/exiting-index-management-requested-but-the-elasticsearch-output-is-not-configured-enabled/290684/3 "2021-12-02T08:41:50Z")

</div>

Hi cjcenizal,

It may look like my problem ... but there is no good answer in the case...

If I understood correctly, apparently, no possibility for filebeat.yml to send logs to logstash ☹

---

<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:** [December 30, 2021, 10:42am UTC](https://discuss.elastic.co/t/exiting-index-management-requested-but-the-elasticsearch-output-is-not-configured-enabled/290684/4 "2021-12-30T10:42:08Z")

</div>

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