Getting Data In

How do keep splunk from removing syslog priority fields?

Chris_R_
Splunk Employee
Splunk Employee

How do keep splunk from removing syslog priority fields? They are removed once indexed into splunk.

Tags (1)
0 Karma
1 Solution

Chris_R_
Splunk Employee
Splunk Employee

There is a optional flag within inputs.conf you can place in any UDP input stanza, such as

[udp://514]

no_priority_stripping = true

This will keep your priority field on any syslog events indexed into splunk via udp port 514

View solution in original post

Chris_R_
Splunk Employee
Splunk Employee

There is a optional flag within inputs.conf you can place in any UDP input stanza, such as

[udp://514]

no_priority_stripping = true

This will keep your priority field on any syslog events indexed into splunk via udp port 514

Chris_R_
Splunk Employee
Splunk Employee

Unfortunately this only works with syslog via UDP inputs.
If using a tcp input, you would have to set up a props/transforms entry to store these fields.

0 Karma

balbano
Contributor

will this also work for SSL? for example:

[splunktcp-ssl:9996]
compressed = true
no_priority_stripping = true

Kindly confirm.

Thanks!

Brian

0 Karma
Get Updates on the Splunk Community!

Enter the Dashboard Challenge and Watch the .conf24 Global Broadcast!

The Splunk Community Dashboard Challenge is still happening, and it's not too late to enter for the week of ...

Join Us at the Builder Bar at .conf24 – Empowering Innovation and Collaboration

What is the Builder Bar? The Builder Bar is more than just a place; it's a hub of creativity, collaboration, ...

Combine Multiline Logs into a Single Event with SOCK - a Guide for Advanced Users

This article is the continuation of the “Combine multiline logs into a single event with SOCK - a step-by-step ...