Splunk Search

Excluding rows based on field combination

jbdumoulin
Engager

Hello splunkers !

Today I'm building a report, in which I'm tasked to exclude some specific results. These are typical windows authentication logs.
I have certain IP's, and logon type, which when they match should be excluded.

For instance, let's say I have an authentication from IP 195.16.108.1 and a logon type 4, I must exclude it from the report. But I can't specify in my alert

ip="195.16.108.1" AND logon_type!=4

That would only select IP 195.16.108.1 while I want to keep every IP, except 195.16.108.1 when logon type equals 4.

I found a solution with the eval function :

 ... request ...|   eval exclude=if(( ip="195.16.108.1" AND logon_type="4"), "true", "false")) | where exclude!="true" | ... do some formating ...

I wonder then : isn't there another solution to my problem ? Because this one sounds counter intuitiv, having to create a new field with a specific value only to sort which row to keep and which ones to exclude.

Tags (2)
0 Karma
1 Solution

gcusello
SplunkTrust
SplunkTrust

Hi jbdumoulin,
try to use parenthesis:

index=my_index NOT (ip="195.16.108.1" logon_type=4)
| ...

Bye.
Giuseppe

View solution in original post

gcusello
SplunkTrust
SplunkTrust

Hi jbdumoulin,
try to use parenthesis:

index=my_index NOT (ip="195.16.108.1" logon_type=4)
| ...

Bye.
Giuseppe

jbdumoulin
Engager

Thanks, really simple solution indeed.

0 Karma
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!

Splunk AI Assistant for SPL vs. ChatGPT: Which One is Better?

In the age of AI, every tool promises to make our lives easier. From summarizing content to writing code, ...

Data Persistence in the OpenTelemetry Collector

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

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 ...