Splunk Search

Filtering Unwanted Events

daniel_augustyn
Contributor

I've been trying to filter unwanted events on a heavy forwarder from being sent to indexers. I followed the instructions which I found in here http://docs.splunk.com/Documentation/Splunk/6.4.3/Forwarding/Routeandfilterdatad, more specifically, I followed this:

Keep specific events and discard the rest
This scenario is opposite to the previous scenario. In this example, you use two transforms to keep only the sshd events. One transform routes sshd events to indexQueue, while another routes all other events to nullQueue.

Note: In this example, the order of the transforms in props.conf matters. The null queue transform must come first; if it comes later, it will invalidate the previous transform and route all events to the null queue.

  1. In props.conf:

[source::/var/log/messages]
TRANSFORMS-set= setnull,setparsing
2. In transforms.conf:

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

[setparsing]
REGEX = [sshd]
DEST_KEY = queue
FORMAT = indexQueue
1. Restart Splunk Enterprise.

But it doesn't work, can someone tell me where is the issue? This is my stanza:

props.conf

[source::/var/log/messages]
TRANSFORMS-null = setnull, setparsing

transforms.conf

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

[setparsing]
REGEX = splunk_agent.py
DEST_KEY = queue
FORMAT = indexQueue

Tags (1)
0 Karma
1 Solution

jconger
Splunk Employee
Splunk Employee

Just a quick first guess, it looks like your REGEX is wrong for [setparsing]. The "." is a special character for regex, so you need to escape it like so:

REGEX = splunk_agent\.py

View solution in original post

woodcock
Esteemed Legend

This should work (although you should escape the . character as the other answer indicates. This should be deployed to your Indexers and each splunk instance there has to be bounced. Even so ONLY DATA THAT IS INDEXED AFTER THE BOUNCE will be correct. The earlier data is already in and will not be effected.

0 Karma

jconger
Splunk Employee
Splunk Employee

Just a quick first guess, it looks like your REGEX is wrong for [setparsing]. The "." is a special character for regex, so you need to escape it like so:

REGEX = splunk_agent\.py
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!

[Puzzles] Solve, Learn, Repeat: Character substitutions with Regular Expressions

This challenge was first posted on Slack #puzzles channelFor BORE at .conf23, we had a puzzle question which ...

Splunk Community Badges!

  Hey everyone! Ready to earn some serious bragging rights in the community? Along with our existing badges ...

[Puzzles] Solve, Learn, Repeat: Matching cron expressions

This puzzle (first published here) is based on matching timestamps to cron expressions.All the timestamps ...