Getting Data In

Null Filtering Not Working

iamDT03
Engager

Greetings all. I am having some trouble getting syslog data to filter with regards to nullQueue. Below are what my config files look like and some additional troubleshooting I've taken so far.

inputs.conf

[udp://5514]
connection_host = ip
index = org_index
sourcetype = cisco:firepower:syslog

 

props.conf

[source::udp:5514]
TRANSFORMS-set= setnull,setparsing

 

transforms.conf

[setnull]
REGEX = .
DEST_KEY = queue
FORMAT = nullQueue

[setparsing]
REGEX = \%FTD-\d-(430002|430003)
DEST_KEY = queue
FORMAT = indexQueue

 

My environment flows Firepower syslog > Heavy Fwd (on prem) > Splunk Cloud and the above configs are on the Heavy Fwd.

In the syslog stream, there are "Correlation Event" logs I am trying to drop. Above I am trying to ingest only message ID's of 430002 and 430003 and drop everything else, however, Correlation Events are still coming in. I've also tried the alternative where I'm targeting Correlation Event in the regex in an effort to drop them, also unsuccessful. Below are some additional troubleshooting steps I've taken.

  • reformatting the source as [source::udp://5514] in props.conf
  • removed spaces before and after the equals signs for each attribute
  • removed the line "REGEX = ." in transforms.conf
  • tried the sourcetype in props.conf, so [cisco:firepower:syslog]
  • tried different regex matches, using regex101
  • restarting Heavy Fwd after each change

Here is the Splunk Doc I've been working with primarily: https://docs.splunk.com/Documentation/Splunk/8.1.0/Forwarding/Routeandfilterdatad#Discard_specific_e...

Any help is greatly appreciated!

Labels (4)
0 Karma
1 Solution

iamDT03
Engager

This issue has been resolved. The [setnull] transform stanza name was conflicting with another transform stanza from a separate add-on. Making the following changes to props.conf and transforms.conf remedied the problem.

#props.conf
[source::udp:5514]
TRANSFORMS-set= dropEvents,setparsing

#transforms.conf
[dropEvents]
REGEX = .
DEST_KEY = queue
FORMAT = nullQueue

[setparsing]
REGEX = \%FTD-\d(430002|430003)
DEST_KEY = queue
FORMAT = indexQueue

View solution in original post

0 Karma

iamDT03
Engager

This issue has been resolved. The [setnull] transform stanza name was conflicting with another transform stanza from a separate add-on. Making the following changes to props.conf and transforms.conf remedied the problem.

#props.conf
[source::udp:5514]
TRANSFORMS-set= dropEvents,setparsing

#transforms.conf
[dropEvents]
REGEX = .
DEST_KEY = queue
FORMAT = nullQueue

[setparsing]
REGEX = \%FTD-\d(430002|430003)
DEST_KEY = queue
FORMAT = indexQueue
0 Karma
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!

Quantify Your Splunk Investment Impact: Introducing Savings Metrics to Value Insights

Building on the foundation established in our initial Value Insights releases, we are introducing the Savings ...

Event Series: Telemetry Pipeline Management

Balancing Scale and Spend: Gaining Control Over High-Volume Metrics in Splunk Observability Cloud As ...

Kick the Tires Before You Commit: A Hands-On Tour of the Splunk Observability Cloud ...

Evaluating an enterprise observability platform usually goes like this: fill out a form, get a free trial with ...