If you're using Elastic Search to ingest a lot of data then you've probably got a Logstash pipeline in action to help you streamline this.

If your logstash pipeline depends on some custom config, and you want to be able to update this config without rebooting logstash then this method is a neat way of doing that.

Logstash introduced the feature of multiple pipelines in Logstash 6. And, in the docs you can see some of the usecases and patterns for multiple pipelines.

My suggestion is a new pattern to create a config pipeline that checks for config updates on a set schedule and then feeds …