Getting Data In

UDP and TCP input behaving differently.

steveta_uk
Explorer

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?

Tags (3)
0 Karma

steveta_uk
Explorer

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

Get Updates on the Splunk Community!

Splunk Observability Cloud’s AI Assistant in Action Series: Analyzing and ...

This is the second post in our Splunk Observability Cloud’s AI Assistant in Action series, in which we look at ...

Elevate Your Organization with Splunk’s Next Platform Evolution

 Thursday, July 10, 2025  |  11AM PDT / 2PM EDT Whether you're managing complex deployments or looking to ...

Splunk Answers Content Calendar, June Edition

Get ready for this week’s post dedicated to Splunk Dashboards! We're celebrating the power of community by ...