Splunk Search

Regex is kicking my butt

cdupuis123
Path Finder

So I'm attempting to drop events from the windows security logs at the indexer so I've created a props.conf that is this:


[source::WinEventLog:Security]
TRANSFORMS-set=setnull, setparsing

and my transforms.conf is:

Exclude windows events

[WinEventLog:Security]
REGEX = (?m) EventCode=(5156).
DEST_KEY = queue
FORMAT = nullQueue

So I'm a Splunk newbie and have struggled/searched/restarted my test instance countless times with still no success. These conf files are in the /opt/splunk/etc/system/local/ and I've yet to even get one event to hit the null queue??? Help!!! thanks in advance

Tags (1)
0 Karma

cdupuis123
Path Finder

Any idea why this stopped working? Where do I start troubleshooting?

0 Karma

kristian_kolb
Ultra Champion

Yes. (5125|4267|1337) etc

I don't know if there is a risk that you'll match 5-digit EventCodes by accident, i.e. 1234 could also match 12345 Might want to add \b at the end of your string.

REGEX=(?m)EventCode=(1234|3456|6789)\b

0 Karma

cdupuis123
Path Finder

Awesome, thanks Kristian

0 Karma

cdupuis123
Path Finder

Awesome, thanks Kristian

Now to add other events I just | them correct?

0 Karma

kristian_kolb
Ultra Champion

The problem lies in how you name/define the transform. In props.conf, you call for two transforms to take place. But these are not found in transforms.conf. Also, for wineventlogs, you do not need to do source:: in props.

And you don't need the setparsing transform either. From the example in the docs, that is used when you want discard all events (to the nullQueue), and then change back to the parsingQueue for those events that match the regex.

Try this instead.

props.conf

[WinEventLog:Security] 
TRANSFORMS-set=setnull

transforms.conf

[setnull] 
REGEX = (?m)EventCode=5156 
DEST_KEY = queue 
FORMAT = nullQueue

Hope this helps,

K

kristian_kolb
Ultra Champion

This operation takes place during the parsing phase. So the configuration must be on the first of the following in your chain from source log to indexed data; a Heavy Forwarder or an Indexer. See the following page;

http://wiki.splunk.com/Where_do_I_configure_my_Splunk_settings

No, dropped data does not count towards the license.

0 Karma

adrianathome
Communicator

Would this need to go on a indexer or search head in a cluster? Does the dropped data count toward license?

0 Karma

gfuente
Motivator

Hello

EDITED:

Follow Kristian answer...

Regards

0 Karma
Get Updates on the Splunk Community!

Index This | Why did the turkey cross the road?

November 2025 Edition  Hayyy Splunk Education Enthusiasts and the Eternally Curious!   We’re back with this ...

Enter the Agentic Era with Splunk AI Assistant for SPL 1.4

  🚀 Your data just got a serious AI upgrade — are you ready? Say hello to the Agentic Era with the ...

Feel the Splunk Love: Real Stories from Real Customers

Hello Splunk Community,    What’s the best part of hearing how our customers use Splunk? Easy: the positive ...