topic How can eventdata from specific sourcetypes be forwarded to syslog on a heavy forwarder? in Getting Data In

How can eventdata from specific sourcetypes be forwarded to syslog on a heavy forwarder?

tylergps — Thu, 13 Aug 2015 15:38:21 GMT

I'm trying to forward Windows logs from a Splunk indexer over to a syslog server. The indexer parses both Windows and Linux logs. I would like to only send events from a set of Windows sourcetypes over to syslog. I have tried configuring outputs.conf, props.conf, and transforms.conf as described in the guide for sending data to third party systems but don't believe it's forwarding properly.

outputs.conf (The syslog server listens on 515)

[syslog:win_syslog_group]
server = 10.10.6.13:515

props.conf

[sourcetype::win*]
TRANSFORMS-win = send_to_syslog

transforms.conf

[send_to_syslog]
REGEX = .
DEST_KEY =  _SYSLOG_ROUTING
FORMAT = win_syslog_group

Re: How can eventdata from specific sourcetypes be forwarded to syslog on a heavy forwarder?

Raschko — Thu, 13 Aug 2015 17:30:17 GMT

Did you had a look on the following option in the outputs.conf documentation:

syslogSourceType = <string>

As you obviously don't have syslog logdata, Splunk will possibly add a correct syslog header (at least timestamp+host) to your logs.

Unfortunately I don't know how it is handling the bunch of line breaks.

As rroberts suggests I would prefer TCP routing too, using the tcpout stanzas.

Re: How can eventdata from specific sourcetypes be forwarded to syslog on a heavy forwarder?

cleelakrishna — Tue, 29 Sep 2020 14:54:20 GMT

the props.conf should be some thing like this
[sourcetype:win*]
TRANSFORMS-win = send_to_syslog