Deployment Architecture

prevent specific syslog from routing to 3rd party vendor using UDP:514

afamuyiwa
Engager

Is it possible to prevent specific logs from routing to a 3rd party vendor? We have IPS system that is generating too much logs for our 3rd party vendor. Logs appear fine in our Splunk environment. My only dilemma is that our heavy forwarder receives logs from various network devices sending logs using UDP:514. Other than changing the port number on our IPS systems is their another way to use props.conf and transform.conf to avoid sending logs to a 3rd party vendor and keep the logs in Splunk only?

Tags (1)
0 Karma
1 Solution

starcher
SplunkTrust
SplunkTrust

The best way is log to a syslog receiver such as syslog-ng or rsylsog. Write data to files and use the Universal forwarder to pick up the logs. It is best to avoid taking syslog straight into Splunk with a network input.

View solution in original post

0 Karma

starcher
SplunkTrust
SplunkTrust

The best way is log to a syslog receiver such as syslog-ng or rsylsog. Write data to files and use the Universal forwarder to pick up the logs. It is best to avoid taking syslog straight into Splunk with a network input.

0 Karma
Get Updates on the Splunk Community!

Index This | I am a number, but when you add ‘G’ to me, I go away. What number am I?

March 2024 Edition Hayyy Splunk Education Enthusiasts and the Eternally Curious!  We’re back with another ...

What’s New in Splunk App for PCI Compliance 5.3.1?

The Splunk App for PCI Compliance allows customers to extend the power of their existing Splunk solution with ...

Extending Observability Content to Splunk Cloud

Register to join us !   In this Extending Observability Content to Splunk Cloud Tech Talk, you'll see how to ...