Splunk Search

Subsearch with multiple field matching

andrewkenth
Communicator

Everyday I bring in events (with a logon id, USER below) and a list of approved users. I want to compare the 2 lists together and show unmatched USER fields, but only for the same date between the event list and the approved users list comes in. Currently I am matching but I seem to be joining across all dates. How do I limit the join to only the same date (and USER)?

index=charlesriver sourcetype=CrdApp_Events EVENT=LOGIN 
| bucket span=1d _time 
| stats count first(_time) as Date by USER 
| search NOT 
   [search index=charlesriver sourcetype=CrdApp_Users 
   | bucket span=1d _time 
   | stats count first(_time) as Date by USER_NAME
   | table USER_NAME|rename USER_NAME as USER]
Tags (2)
0 Karma

somesoni2
Revered Legend

One option can be to use join

index=charlesriver sourcetype=CrdApp_Events EVENT=LOGIN 
| bucket span=1d _time 
| stats count first(_time) as Date by USER 
| join Date,USER  [search index=charlesriver sourcetype=CrdApp_Users 
   | bucket span=1d _time 
   | stats count first(_time) as Date by USER_NAME
   | table USER_NAME,Date|rename USER_NAME as USER |eval filter=1]
|where NOT filter=1 | fields - filter
0 Karma

somesoni2
Revered Legend

Can you try like this (added Date field in subsearch)

index=charlesriver sourcetype=CrdApp_Events EVENT=LOGIN | bucket span=1d _time | stats count first(_time) as Date by USER |search NOT [search index=charlesriver sourcetype=CrdApp_Users | bucket span=1d _time | stats count first(_time) as Date by USER_NAME| table Date,USER_NAME|rename USER_NAME as USER]

0 Karma
Get Updates on the Splunk Community!

Index This | What’s a riddle wrapped in an enigma?

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

BORE at .conf25

Boss Of Regular Expression (BORE) was an interactive session run again this year at .conf25 by the brilliant ...

OpenTelemetry for Legacy Apps? Yes, You Can!

This article is a follow-up to my previous article posted on the OpenTelemetry Blog, "Your Critical Legacy App ...