Getting Data In

Forwarding selected events from Indexer to thrid-party application

tobiasvollrath
Explorer

Hi,
in our system we have same universal forwarders, one indexer and a third-party system that expect only events in syslog-format.

How can I send selected events from the indexer via syslog to my third-party system. That selected events should not save in the indexer. All other events should be indexed.

Is there a way to do this?

I try this configuration, but the index sent all events via syslog.

#inputs.conf
[splunktcp-ssl://9997]
_SYSLOG_ROUTING = syslog_test

#outputs.conf
[syslog:syslog_test]
server = 192.168.0.42:10514

Thanks for your help,
with best greetings

Tobias

Tags (2)

tobiasvollrath
Explorer

It works! Thanks a lot.

But there is one open querstion:

The indexer should not index the events wich go out via syslog. Is this posible?

0 Karma

fbl_itcs
Path Finder

Hi,

you can do that with a transformation.

You define the output in your outputs.conf. Then you create a transformation using props.conf and transforms.conf:

props.conf:

[sourcetypename OR host::HOSTNAME OR source::SOURCENAME]
TRANSFORMS-syslog = syslog_out

transforms.conf

[syslog_out]
REGEX = REGEX_TO_FILTER_EVENTS_GOES_HERE
DEST_KEY=_SYSLOG_ROUTING
FORMAT=syslog_test

0 Karma
Get Updates on the Splunk Community!

Automatic Discovery Part 1: What is Automatic Discovery in Splunk Observability Cloud ...

If you’ve ever deployed a new database cluster, spun up a caching layer, or added a load balancer, you know it ...

Real-Time Fraud Detection: How Splunk Dashboards Protect Financial Institutions

Financial fraud isn't slowing down. If anything, it's getting more sophisticated. Account takeovers, credit ...

Splunk + ThousandEyes: Correlate frontend, app, and network data to troubleshoot ...

 Are you tired of troubleshooting delays caused by siloed frontend, application, and network data? We've got a ...