Getting Data In

Forwarding to a third party syslog server based on both host, sourcetype and regex

edoardo_vicendo
Builder

We have to forward some data from a Splunk Heavy Forwarder to a third party syslog server.

This is possible as indicated here:

https://docs.splunk.com/Documentation/Splunk/8.0.6/Forwarding/Forwarddatatothird-partysystemsd

 

The challenge is to select only some files from a particular host and forward only the logs that contain a particular string.

Here is what we were able to achieve (basically 2 rules out of 3, so some files that contain a particular string), I don’t know if it is possible to add in some way a reference also for the host.

Do you know if it is feasible?

 

outputs.conf
[syslog:syslog_target]
type = udp
server = 111.222.333.444:514

props.conf
[source::/path/of/myfile/*filename.log]
TRANSFORMS-syslog_forward = syslog_forward_rule

transforms.conf
[syslog_forward_rule]
REGEX = www\.mywebsite\.com
DEST_KEY = _SYSLOG_ROUTING
FORMAT = syslog_target

 

Thanks a lot,

Edoardo

0 Karma
1 Solution

edoardo_vicendo
Builder

@thambisetty Thanks for your feedback.
Basically there is no way to use host sourcetype and regex all together, unless you have the host:

  • in the event itself (that is not our case) --> so that you can filter with the REGEX in the transforms.conf
  • in the path name (that is not our case as well) --> so that you can directly filter in source stanza in props.conf

View solution in original post

0 Karma

thambisetty
SplunkTrust
SplunkTrust

I don’t think you can make use of host and source combinations in single props stanza.

if source specified in props matches events coming from those hosts you want to include and event contains host value then you can modify your regex in transforms to identify events you want to forward to syslog.

————————————
If this helps, give a like below.

edoardo_vicendo
Builder

@thambisetty Thanks for your feedback.
Basically there is no way to use host sourcetype and regex all together, unless you have the host:

  • in the event itself (that is not our case) --> so that you can filter with the REGEX in the transforms.conf
  • in the path name (that is not our case as well) --> so that you can directly filter in source stanza in props.conf
0 Karma
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Mastering Threat Intelligence in ES 8.5, Splunk AI Assistant v2, and More from Splunk ...

Splunk Lantern is Splunk’s customer success center that provides practical guidance from Splunk experts on key ...

Break the Build: Inside the KubeDoom Lounge at .conf26

    You step up to the machine. The pixelated corridors of a certain 1993 FPS load in front of you, EMP Pulse ...

Splunk Auto Ingestion Parallel Pipeline Scaling

Why this feature matters Many Splunk environments experience ingestion pressure long before the host is fully ...