# Several inputs for modules
**URL:** https://discuss.elastic.co/t/several-inputs-for-modules/301851
**Category:** Beats
**Tags:** beats-module, filebeat
**Created:** [April 7, 2022, 9:55am UTC](https://discuss.elastic.co/t/several-inputs-for-modules/301851 "2022-04-07T09:55:04Z")
**Posts on this page:** 2
**Page:** 1
### Author:  [@Thermi](https://discuss.elastic.co/u/Thermi)
#### Post date: [April 7, 2022, 9:55am UTC](https://discuss.elastic.co/t/several-inputs-for-modules/301851/1 "2022-04-07T09:55:04Z")
Hello,
I need to configure several inputs for any particular module, but most modules only have one, or generally a way to specify the mode/type/protocol of one (syslog over TLS, syslog over UDP, reading from a log file, ...). I want to have several though, so just overriding the keys won't help me with solving that. Is there a standard way to solve that problem? The reason I want to do that is I want to use the same configuration for inputs in several different use cases. Different setups require/support syslog via TCP, or via UDP, and I want to avoid having to modify the configuration each time.
Examples for these problems are the modules for Check Point and Palo Alto.
If anybody has a good solution to the problem, please let me know. I want to avoid customizing or altering large parts of each module. So a general way to solve it that avoids having to touch every single module would be great.
Links: [beats/firewall.yml at master · elastic/beats · GitHub](https://github.com/elastic/beats/blob/master/x-pack/filebeat/module/checkpoint/firewall/config/firewall.yml)
[beats/input.yml at master · elastic/beats · GitHub](https://github.com/elastic/beats/blob/master/x-pack/filebeat/module/panw/panos/config/input.yml)
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [May 5, 2022, 11:55am UTC](https://discuss.elastic.co/t/several-inputs-for-modules/301851/2 "2022-05-05T11:55:20Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.