# Custom pipeline settings with Centralised Pipeline Management **URL:** https://discuss.elastic.co/t/custom-pipeline-settings-with-centralised-pipeline-management/371001 **Category:** Logstash **Created:** [November 25, 2024, 1:58am UTC](https://discuss.elastic.co/t/custom-pipeline-settings-with-centralised-pipeline-management/371001 "2024-11-25T01:58:30Z") **Posts on this page:** 1 **Page:** 1
### Author: ![garethhumphriesgkc](https://avatars.discourse-cdn.com/v4/letter/g/eb8c5e/32.png) [@garethhumphriesgkc](https://discuss.elastic.co/u/garethhumphriesgkc) #### Post date: [November 25, 2024, 1:58am UTC](https://discuss.elastic.co/t/custom-pipeline-settings-with-centralised-pipeline-management/371001/1 "2024-11-25T01:58:30Z")
Hi, We're looking at moving our existing pipelines from git to to Kibana, using "Centralised Pipeline Management". I tried replicating them in Kibana, but only very basic settings were present - I couldn't set any of our custom config (e.g., dead letter queue). I then went to create them through the API with all my custom settings present, which appeared to work but for a couple of things. Minor annoyances are: - If you subsequently edit them through Kibana, all those custom settings are lost. - The "Last Modified" time can't be set (and doesn't default to) "now" - you have to enter the entire timestamp each time. More significantly though, when I start logstash I get a lot of lines like: ```auto [logstash.configmanagement.elasticsearchsource] Ignoring unsupported or unknown pipeline settings 'dead_letter_queue.enable' [logstash.configmanagement.elasticsearchsource] Ignoring unsupported or unknown pipeline settings 'dead_letter_queue.retain.age' [logstash.configmanagement.elasticsearchsource] Ignoring unsupported or unknown pipeline settings 'dead_letter_queue.flush_interval' [logstash.configmanagement.elasticsearchsource] Ignoring unsupported or unknown pipeline settings 'dead_letter_queue.storage_policy' [logstash.configmanagement.elasticsearchsource] Ignoring unsupported or unknown pipeline settings 'queue.drain' ``` Am I to assume based on this that these settings can't be set on a pipeline managed centrally? If so, how do people work around this?