ES ingest node per input

Filebeat modules come with matching ES ingest node configuration. Filebeat routes module specific input through that matching ingest node on ES.
I would like to do the same for normal inputs, defining with the input a specific ingest node to route through-
I understand that its possible to define an Elsaticsearch output such that a tag defined with an input can be used for specifiying an ingest node at the output.
I would like to know if these are different mechanisms and how i can avoid messing up the module based ingest node routing with such a setup.

Hey @ccmsi welcome to discuss :slight_smile:

Filebeat modules route events to specific ingest pipelines, not to specific nodes. It is also possible to select a pipeline per input. When reading logs from files you can use the pipeline option for that.

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