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

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!

Kubernetes Alerts That Work Out of the Box with AutoDetect detectors in Splunk ...

A deployment rolls out slowly, one pod sits not ready for a few minutes, and whoever is on call gets an alert ...

Observability at Your Fingertips Directly From Splunk Platform—for Free

At .conf, we announced our roadmap to bring observability foundations to Splunk Platform. Bringing metrics and ...

Accelerate Splunk App Development with AI

  Learn how to automate the repetitive parts of your build cycle.   Watch On-Demand   Replay the Accelerate ...