topic Re: unable to send windows events from splunk server to third party syslog server in Getting Data In

unable to send windows events from splunk server to third party syslog server

cleelakrishna — Tue, 29 Sep 2020 14:38:41 GMT

tried below configurations to forward the data from SPLUNK server to syslog server(third party) , but no data in syslog server. can you please help me out on this where i'm going wrong

props.conf:

[WinEventLog:Security]
TRANSFORMS-routing = win_security_syslog

[WinEventLog:Application]
TRANSFORMS-routing = win_application_syslog

[WinEventLog:System]
TRANSFORMS-routing = win_system_syslog

transforms.conf :

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

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

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

outputs.conf:

[syslog:win_syslog_group]
server = abc:514
type=udp

Re: unable to send windows events from splunk server to third party syslog server

maciep — Sun, 02 Jul 2017 13:06:09 GMT

do you have that config on a heavy forwarder or indexer? don't believe syslog processing is available on universal forwarder.

Re: unable to send windows events from splunk server to third party syslog server

maraman_splunk — Sun, 02 Jul 2017 19:10:25 GMT

Hi,

I'm afraid there's no easy solution.

your configuration looks good but doesn't apply because winevent log collection is done in a structured way -> so data is going out of your UF already parsed ...
when received later on (on a HF for example which can send syslog) -> splunk doesn't reanalyze the data twice.
but the original UF can't directly send syslog...

so you should :
- keep a uf for collection
- send your data normally up to your indexer(s).
- somewhere between your uf and indexer(s), clone the data (a uf can do it) and send it to 1 or more specialized HF that will do the syslog and other specific things (ie transforms) you'll need to make windows event fit in syslog (because that's not natural to make multiline go in a protocol which is traditionally for one line events...)
- apply your syslog stuff above on the specialized HF/Syslog

look at this post as a guideline
https://answers.splunk.com/answers/5528/forwarding-select-data-in-my-environment.html

beware that you should not modify the settings before cloning as setting the route parameters on input should normally not be modified.(because it's easy to break things this way)

Good luck and happy splunking !