"no_priority_stripping = true" is not working

[kondou]

I enabled "no_priority_stipping" in inputs.conf with restarting splunk, but still UDP syslog messages do not include priority level at the head of log.

Does anyone know how to enable this?

[mic]

I know that this was posted quite a long time ago, but I am sure that this works in 5.0.3

inputs.conf without "no_priority_stripping"

[udp://45515]
sourcetype = syslog
connection_host = ip
index = custom_orig

running the search " ./splunk search "index=custom_orig | eval T=_time | convert ctime(T) | eval IT=_indextime | eval R=_raw | sort IT | table T sourcetype host R | sort by sourcetype"", I got

         T           sourcetype      host                             R
------------------- ------------ ------------ -------------------------------------------------
06/13/2013 19:57:53 kinda-syslog 10.160.44.71 Jun 13 19:57:53 10.160.44.71  ERROR login failure

inputs.conf with "no_priority_stripping = true"

[udp://45515]
sourcetype = syslog
connection_host = ip
index = custom_orig
no_priority_stripping = true

running the search "./splunk search "index=custom_orig | eval T=_time | convert ctime(T) | eval IT=_indextime | eval R=_raw | sort IT | table T sourcetype host R | sort by sourcetype"", I got

         T          sourcetype     host                R
------------------- ---------- ------------ ------------------------
06/13/2013 20:00:47 syslog     10.160.44.71 <13> ERROR login failure

this should work, try it out

[Genti]

make sure that the syslog messages are actually coming with the priority level included. Tell syslog to write to file and examine the file. If the priority is not showing up there, then it is not a splunk issue. You have to find out how to tell syslog to actually send the priority flag over.

Cheers!

[mchang_splunk]

Details in docs.splunk.com:
http://docs.splunk.com/Documentation/Splunk/latest/Data/Monitornetworkports

no_priority_stripping = [true|false]

Setting for receiving syslog data.
If this attribute is set to true, Splunk does NOT strip the syslog field from received events.
Depending on how this attribute is set, Splunk sets event timestamps differently:
When set to true, Splunk honors the timestamp as it comes from the source.
When set to false, Splunk assigns events the local time.
Default is false (Splunk strips ).

[kondou]

I examined the syslog packet coming into udp:514 by tcpdump, and it actually includes priority. So, I suspect this is a splunk issue.