Hi, If I set pipeline.workers > 1 then event dependent configuration , "%{}", appears to be disabled. Here is my test case. #!/bin/bash # This works export TIX_VERSION=1 gunzip --stdout tmp/cart.gz | logstash --pipeline.workers 1 --path.config=logstash/cart_logstash.conf # This does not export TI…

Event dependent configuration broken with multiple pipelines?

magnusbaeck (Magnus Bäck) August 1, 2018, 6:08am 4

Yes, that's most likely the case. I've never trusted the autodetect feature.

1 Like

Topic		Replies	Views
Logstash pipeline processing Logstash	6	590	April 4, 2022
Error Running Logstash multiple config Logstash	3	351	December 2, 2022
Logstash pipeline error when processing a csv file Logstash	7	1033	May 8, 2023
Is "worker" configuration for output plugin deprecated? Logstash	6	1108	July 6, 2017
Change pipeline worker node to provide sequence of logs in kibana Logstash	4	630	July 30, 2019

Elasticsearch is a trademark of Elasticsearch BV, registered in the U.S. and in other countries
Trademarks
Terms
Privacy
Brand
Code of Conduct

Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant logo are trademarks of the Apache Software Foundation in the United States and/or other countries.

Event dependent configuration broken with multiple pipelines?

Related topics