# Centralized pipeline configuration lost after license expiry - is there a way to get it back? \[Solved\]

**URL:** <https://discuss.elastic.co/t/centralized-pipeline-configuration-lost-after-license-expiry-is-there-a-way-to-get-it-back-solved/128642>\
**Category:** Logstash\
**Created:** [April 19, 2018, 7:21am UTC](https://discuss.elastic.co/t/centralized-pipeline-configuration-lost-after-license-expiry-is-there-a-way-to-get-it-back-solved/128642 "2018-04-19T07:21:41Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![dswinton](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dswinton/32/30157_2.png) [@dswinton](https://discuss.elastic.co/u/dswinton)\
**Post date:** [April 19, 2018, 7:21am UTC](https://discuss.elastic.co/t/centralized-pipeline-configuration-lost-after-license-expiry-is-there-a-way-to-get-it-back-solved/128642/1 "2018-04-19T07:21:41Z")

</div>

Hi Guys,

I've been googling and picking through my Logstash server to try to fix this issue for a couple of hours now and have come up with nothing...

I spent quite a bit of time writing an extensive set of pipeline rules using the centralized configuration feature of X-Pack in Kibana. Previously I had just written them in configuration files, but made the switch so I could edit them more easily in the web UI.

Unfortunately, I didn't realise that the centralised management feature was a paid feature, so as soon as my trial expired those configuration options have now disappeared and my Logstash instance has lost it's configuration. I looked into buying a license, but it's way, _WAY_ out of my price range.

Is there a way to retrieve the pipeline configuration stored in the Centralized Configuration feature so I can just drop it into a text configuration file?

Thanks in advance!

---

<div class="post-metadata">

**Author:** ![shaunak](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/shaunak/32/6643_2.png) [@shaunak](https://discuss.elastic.co/u/shaunak)\
**Post date:** [April 19, 2018, 11:54pm UTC](https://discuss.elastic.co/t/centralized-pipeline-configuration-lost-after-license-expiry-is-there-a-way-to-get-it-back-solved/128642/2 "2018-04-19T23:54:31Z")

</div>

Hmmmm, I haven't tested this but you should be able to make the following request to Elasticsearch:

```auto
GET .logstash/_search

```

This should return your pipeline configurations in the response. If you stored more than 20 pipelines in centralized configuration management, just append `?size=<number_of_pipelines>` to your request.

---

<div class="post-metadata">

**Author:** ![dswinton](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dswinton/32/30157_2.png) [@dswinton](https://discuss.elastic.co/u/dswinton)\
**Post date:** [April 20, 2018, 1:01am UTC](https://discuss.elastic.co/t/centralized-pipeline-configuration-lost-after-license-expiry-is-there-a-way-to-get-it-back-solved/128642/3 "2018-04-20T01:01:35Z")

</div>

Hi @shaunak,

That worked perfectly - thank you very much! 😀

All the pipeline were output by this command. All I had to do was remove some extra escaping from the output, and drop the pipelines into text configuration files.

My Logstash box is now back up and running.  
Very much appreciate your help!

---

<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:** [May 18, 2018, 1:01am UTC](https://discuss.elastic.co/t/centralized-pipeline-configuration-lost-after-license-expiry-is-there-a-way-to-get-it-back-solved/128642/4 "2018-05-18T01:01:53Z")

</div>

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