UDP and TCP input behaving differently.

steveta_uk · ‎12-12-2012

I have a setup with a specific sourcetype defined (rfc5424_syslog), which works fine over TCP, but when exactly the same data is received over UDP is seems to get automatically broken into fields by Splunk which do not match the source type I'm using. Even the _raw fields contains reformatted data, whereas the _raw field from the TCP source is precisely as sent.

Does anyone know what I need to do to stop Splunk automatically reformatting the data when received over UDP?

steveta_uk · ‎01-28-2013

Answer provided by Splunk support, in case anyone else needs it, is to add this line to the inputs.conf entry that specified the UDP port:

no_priority_stripping = true

UDP and TCP input behaving differently.

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

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

Deep Dive: Accelerate threat investigation with Splunk’s AI Assistant in Security

Announcing Modern Navigation: A New Era of Splunk User Experience

Detection Engineering Office Hours: Real-World Troubleshooting & Q&A

Join the Conversation

UDP and TCP input behaving differently.

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

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

Deep Dive: Accelerate threat investigation with Splunk’s AI Assistant in Security

Announcing Modern Navigation: A New Era of Splunk User Experience

Detection Engineering Office Hours: Real-World Troubleshooting & Q&A