# ES ingest node per input
**URL:** https://discuss.elastic.co/t/es-ingest-node-per-input/253816
**Category:** Beats
**Tags:** filebeat
**Created:** [October 30, 2020, 12:14pm UTC](https://discuss.elastic.co/t/es-ingest-node-per-input/253816 "2020-10-30T12:14:20Z")
**Posts on this page:** 3
**Page:** 1
### Author:  [@ccmsi](https://discuss.elastic.co/u/ccmsi)
#### Post date: [October 30, 2020, 12:14pm UTC](https://discuss.elastic.co/t/es-ingest-node-per-input/253816/1 "2020-10-30T12:14:20Z")
Greetings.
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.
---
### Author:  [@jsoriano](https://discuss.elastic.co/u/jsoriano)
#### Post date: [November 3, 2020, 1:13pm UTC](https://discuss.elastic.co/t/es-ingest-node-per-input/253816/2 "2020-11-03T13:13:42Z")
Hey @ccmsi welcome to discuss 🙂
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](https://www.elastic.co/guide/en/beats/filebeat/7.9/filebeat-input-log.html#_pipeline_9) for that.
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [December 1, 2020, 3:13pm UTC](https://discuss.elastic.co/t/es-ingest-node-per-input/253816/3 "2020-12-01T15:13:45Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.