Splunk Search

How to exclude a match in regex - Regex

Kanesol
Explorer

I have this search:

index="blah" source="blah" cs_Referer_="-" NOT(some keyword exclusion here) | regex cs_host="^(\b\d{1,3}.\d{1,3}.\d{1,3}.\d{1,3}\b)+"

and I wish to add this to it as a NOT :

regex cs_uri_stem="\?d=[\w.]+@\w+.\w+"

Not sure how to go about this. Any Input is appreciated.

Tags (1)
1 Solution

hexx
Splunk Employee
Splunk Employee

I think you've got the most reasonable solution already with this search:

index="blah" source="blah" cs_Referer_="-" NOT(some keyword exclusion here) | regex cs_host="^(\b\d{1,3}\.\d{1,3}\.\d{1,3}\.\d{1,3}\b)+" | regex cs_uri_stem="\?d=[\w.]+@\w+.\w+"

Attempting to contract both regular expressions into one probably won't yield any performance benefits.

View solution in original post

hexx
Splunk Employee
Splunk Employee

I think you've got the most reasonable solution already with this search:

index="blah" source="blah" cs_Referer_="-" NOT(some keyword exclusion here) | regex cs_host="^(\b\d{1,3}\.\d{1,3}\.\d{1,3}\.\d{1,3}\b)+" | regex cs_uri_stem="\?d=[\w.]+@\w+.\w+"

Attempting to contract both regular expressions into one probably won't yield any performance benefits.

Kanesol
Explorer

Thanks for confirming that for me. I was hoping for something a little nicer.

0 Karma

Kanesol
Explorer

To update, I've resorted to just adding more and more pipes for each regex which I believe is not optimal but serviceable. I'm hoping someone can come up with a more elegant way 🙂

index="blah" source="blah" cs_Referer_="-" NOT(some keyword exclusion here) | regex cs_host="^(bd{1,3}.d{1,3}.d{1,3}.d{1,3}b)+" | regex cs_uri_stem!="?d=[w.]+@w+.w+"

Career Survey
First 500 qualified respondents will receive a $20 gift card! Tell us about your professional Splunk journey.
Get Updates on the Splunk Community!

Thanks for the Memories! Splunk University, .conf25, and our Community

Thank you to everyone in the Splunk Community who joined us for .conf25, which kicked off with our iconic ...

Data Persistence in the OpenTelemetry Collector

This blog post is part of an ongoing series on OpenTelemetry. What happens if the OpenTelemetry collector ...

Introducing Splunk 10.0: Smarter, Faster, and More Powerful Than Ever

Now On Demand Whether you're managing complex deployments or looking to future-proof your data ...