# Unable to configure Index Lifecycle Management (ILM) with Logstash Elasticsearch output

**URL:** <https://discuss.elastic.co/t/unable-to-configure-index-lifecycle-management-ilm-with-logstash-elasticsearch-output/208564>\
**Category:** Logstash\
**Created:** [November 19, 2019, 7:01pm UTC](https://discuss.elastic.co/t/unable-to-configure-index-lifecycle-management-ilm-with-logstash-elasticsearch-output/208564 "2019-11-19T19:01:37Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![DougR](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dougr/32/48095_2.png) [@DougR](https://discuss.elastic.co/u/DougR)\
**Post date:** [November 19, 2019, 7:01pm UTC](https://discuss.elastic.co/t/unable-to-configure-index-lifecycle-management-ilm-with-logstash-elasticsearch-output/208564/1 "2019-11-19T19:01:37Z")

</div>

I'm simply trying to get ILM to work at the moment with Logstash, Elasticsearch, and Filebeat. Or any other beat.

This is my `elasticsearch` output block:

```bash
output {
    elasticsearch {
        hosts => ["localhost:9200"]
        manage_template => false
        ilm_enabled => true
        ilm_rollover_alias => "filebeat-rollover"
        ilm_pattern => "filebeat-7.4.2-{now/d}-000001"
        ilm_policy => "ilm-default-policy"
    }
}

```

The policy `ilm-default-policy` does exist.

This is what I get in my Logstash logs:

```bash
[2019-11-19T09:36:03,208][INFO][logstash.runner] Starting Logstash {"logstash.version"=>"7.1.1"}
[2019-11-19T09:36:09,054][INFO][logstash.outputs.elasticsearch] Elasticsearch pool URLs updated {:changes=>{:removed=>[], :added=>[http://localhost:9200/]}}
[2019-11-19T09:36:09,363][WARN][logstash.outputs.elasticsearch] Restored connection to ES instance {:url=>"http://localhost:9200/"}
[2019-11-19T09:36:09,409][INFO][logstash.outputs.elasticsearch] ES Output version determined {:es_version=>7}
[2019-11-19T09:36:09,412][WARN][logstash.outputs.elasticsearch] Detected a 6.x and above cluster: the `type` event field won't be used to determine the document _type {:es_version=>7}
[2019-11-19T09:36:09,435][INFO][logstash.outputs.elasticsearch] New Elasticsearch output {:class=>"LogStash::Outputs::ElasticSearch", :hosts=>["//localhost:9200"]}
[2019-11-19T09:36:09,665][FATAL][logstash.runner] An unexpected error occurred! {:error=>#<LogStash::Outputs::ElasticSearch::HttpClient::Pool::BadResponseCodeError: LogStash::Outputs::ElasticSearch::HttpClient::Pool::BadResponseCodeError>, :backtrace=>["/usr/share/logstash/vendor/bundle/jruby/2.5.0/gems/logstash-output-elasticsearch-10.1.0-java/lib/logstash/outputs/elasticsearch/http_client/manticore_adapter.rb:80:in `perform_request'", "/usr/share/logstash/vendor/bundle/jruby/2.5.0/gems/logstash-output-elasticsearch-10.1.0-java/lib/logstash/outputs/elasticsearch/http_client/pool.rb:291:in `perform_request_to_url'", "/usr/share/logstash/vendor/bundle/jruby/2.5.0/gems/logstash-output-elasticsearch-10.1.0-java/lib/logstash/outputs/elasticsearch/http_client/pool.rb:278:in `block in perform_request'", "/usr/share/logstash/vendor/bundle/jruby/2.5.0/gems/logstash-output-elasticsearch-10.1.0-java/lib/logstash/outputs/elasticsearch/http_client/pool.rb:373:in `with_connection'", "/usr/share/logstash/vendor/bundle/jruby/2.5.0/gems/logstash-output-elasticsearch-10.1.0-java/lib/logstash/outputs/elasticsearch/http_client/pool.rb:277:in `perform_request'", "/usr/share/logstash/vendor/bundle/jruby/2.5.0/gems/logstash-output-elasticsearch-10.1.0-java/lib/logstash/outputs/elasticsearch/http_client/pool.rb:285:in `block in Pool'", "/usr/share/logstash/vendor/bundle/jruby/2.5.0/gems/logstash-output-elasticsearch-10.1.0-java/lib/logstash/outputs/elasticsearch/http_client.rb:341:in `exists?'", "/usr/share/logstash/vendor/bundle/jruby/2.5.0/gems/logstash-output-elasticsearch-10.1.0-java/lib/logstash/outputs/elasticsearch/http_client.rb:359:in `rollover_alias_exists?'", "/usr/share/logstash/vendor/bundle/jruby/2.5.0/gems/logstash-output-elasticsearch-10.1.0-java/lib/logstash/outputs/elasticsearch/ilm.rb:91:in `maybe_create_rollover_alias'", "/usr/share/logstash/vendor/bundle/jruby/2.5.0/gems/logstash-output-elasticsearch-10.1.0-java/lib/logstash/outputs/elasticsearch/ilm.rb:10:in `setup_ilm'", "/usr/share/logstash/vendor/bundle/jruby/2.5.0/gems/logstash-output-elasticsearch-10.1.0-java/lib/logstash/outputs/elasticsearch/common.rb:52:in `block in setup_after_successful_connection'"]}
[2019-11-19T09:36:09,696][INFO][logstash.javapipeline] Starting pipeline {:pipeline_id=>"main", "pipeline.workers"=>8, "pipeline.batch.size"=>125, "pipeline.batch.delay"=>50, "pipeline.max_inflight"=>1000, :thread=>"#<Thread:0xffca1e9 run>"}
[2019-11-19T09:36:09,754][ERROR][org.logstash.Logstash] java.lang.IllegalStateException: Logstash stopped processing because of an error: (SystemExit) exit

```

---

<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 17, 2019, 7:01pm UTC](https://discuss.elastic.co/t/unable-to-configure-index-lifecycle-management-ilm-with-logstash-elasticsearch-output/208564/2 "2019-12-17T19:01:42Z")

</div>

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