Hi @gcusello, Sorry for the delay. Did you find a working solution? My suggestion was something like: # inputs.conf
[tcp://10514]
sourcetype = syslog
index = network
[udp://10515]
index = network...
See more...
Hi @gcusello, Sorry for the delay. Did you find a working solution? My suggestion was something like: # inputs.conf
[tcp://10514]
sourcetype = syslog
index = network
[udp://10515]
index = network
sourcetype = infoblox:port
[udp://10516]
index = network
sourcetype = juniper
[udp://10517]
index = network
sourcetype = fgt_log
# outputs.conf
[syslog:infoblox]
server = localhost:10515
type = udp
priority = NO_PRI
[syslog:juniper]
server = localhost:10516
type = udp
priority = NO_PRI
[syslog:fortinet]
server = localhost:10517
type = udp
priority = NO_PRI
# props.conf
[source::tcp:10514]
TRANSFORMS-reroute_syslog = route_infoblox, route_juniper, route_fortinet
# transforms.conf
[route_infoblox]
REGEX = \<\d+\>\w+\s+\d+\s+\d+:\d+\d+:\d+\s+\w+-dns-\w+
DEST_KEY = _SYSLOG_ROUTING
FORMAT = infoblox
[route_juniper]
REGEX = ^\<\d+\>\d+\s+\d+-\d+-\d+\w+:\d+:\d+\.\d+\w(\+|-)\d+:\d+\s\w+-edget-fw
DEST_KEY = _SYSLOG_ROUTING
FORMAT = juniper
[route_fortinet]
REGEX = ^\<\d+\>date\=\d+-\d+-\d+\s+time\=\d+:\d+:\d+\s+devname\=\"[^\"]+\"\s+devid
DEST_KEY = _SYSLOG_ROUTING
FORMAT = fortinet All events sent to the 10514/tcp input will hit the specified transforms. On match, the event will be reroute to one of the udp inputs using _SYSLOG_ROUTING. If the default syslog output queue size (97 KiB) isn't large enough, you can scale by increasing parallelIngestionPipelines (and resources if the HF performs other functions). I haven't tried increasing the syslog output queue size in some time, but it was hard-coded in the past. You can also use tcp inputs and type = tcp in syslog outputs, but when forwarding packets locally, the risk of loss comes from buffer/queue overruns, not the network. All that said, rsyslog or syslog-ng (my preference) installed on the same host is a better solution. You can preferably write and monitor files, or you can relay to local Splunk tcp/udp inputs. If you use files, you'll need adequate local storage for buffering and e.g. logrotate to manage retention. Both rsyslog and syslog-ng have mature and robust parsing languages.