Splunk Search

Use of "NOT" vs "!="

rtadams89
Contributor

I'm working on a search which should return all events, except those where the "User_Name" or the "Account_Name" fields end with a "$".

If I use this

(NOT (User_Name="*$" OR Account_Name="*$"))

I get the reuslts I expect. However if I use

User_Name!="*$" Account_Name!="*$"

I don't get any results.

In my mind, those two statements should produce the same results. What is it I'm not seeing?

1 Solution

Ayn
Legend

The difference is that with != it's implied that the field exists, but does not have the value specified. So if the field is not found at all in the event, the search will not match.

NOT field= on the other hand will check if the field has the specified value, and if it doesn't for whatever reason, it will match.

View solution in original post

Ayn
Legend

The difference is that with != it's implied that the field exists, but does not have the value specified. So if the field is not found at all in the event, the search will not match.

NOT field= on the other hand will check if the field has the specified value, and if it doesn't for whatever reason, it will match.

debabratp
New Member

It helps a lot.

0 Karma

Ayn
Legend

Yeah, because that would say 'User_Name exists and it doesn't match "*$" OR Account_Name exists and it doesn't match "*$"'.

rtadams89
Contributor

Ahh. Well that helps. So jsut for further clarification, I could solve the problem and still use != if I did:

User_Name!="*$" OR Account_Name!="*$"

Assuming I know for sure that all events will have one (and only one) of those fields.

0 Karma
Get Updates on the Splunk Community!

Join Us for Splunk University and Get Your Bootcamp Game On!

If you know, you know! Splunk University is the vibe this summer so register today for bootcamps galore ...

.conf24 | Learning Tracks for Security, Observability, Platform, and Developers!

.conf24 is taking place at The Venetian in Las Vegas from June 11 - 14. Continue reading to learn about the ...

Announcing Scheduled Export GA for Dashboard Studio

We're excited to announce the general availability of Scheduled Export for Dashboard Studio. Starting in ...