For some obscure reason,
when I add a pipeline to an integration via Custom configurations (lower red rectangle in first screen below), it is not triggered when the policy integration output is set to logstash (second screen below).
I need to switch it back to Elasticsearch for the ingest pipeline to kick in.
Looks like I cant have both Logstash output AND ingest pipeline set this way, for some reason.
Which is a shame because they offer different degrees of granularity (integration level pipelines, policy level pipelines)
PS : I am quasi sure I made both work at the same time at some point but I can't seem to make it work again.
If you ouput from the agent to logstash then events come from logstash to elasticsearch, I think it was possible to pass pipelines but your case proves otherwise.
I think it would be best to have the pipeline linked to your index template. That way the source of the events is irrelevant and your events should be processed by the pipeline when they are sent to the index linked to the index template.
edit: are you sure you have configured pipeline => "%{[@metadata][pipeline]}" in your logstash ouput?
If this is what your mentioning, then yes, you need to do that.
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.