Splunk Dev

Nested Search Query

kartiksha
Explorer

Hi,

I need a way to merge these two queries to get a proper report with having to run them separately.

First Query to generate a list of IDs:
source="Source1" receiverAddress=test@test.com| dedup "attachments{}.UniqueID"|table "attachments{}.UniqueID"

Results (EX):
1e32fdc2-5519-4e3a-2233-88e49a21e663

Second Query to generate actual results:
source="Source2" UniqueID=1e32fdc2-5519-4e3a-2233-88e49a21e663 CreateEvent|dedup UniqueID| timechart span=1d count(UniqueID) as "Test"

Results (EX):
_time Test
2017-05-29 1

I tried to use Nested Query like:
source="Source2" [search source="Source1" receiverAddress=test@test.com| dedup "attachments{}.UniqueID"|table "attachments{}.UniqueID"] CreateEvent|dedup UniqueID| timechart span=1d count(UniqueID) as "Test"

But unfortunately it returns nothing. Is there something I'm doing incorrectly?

Thanks
Kartik Sharma

Tags (1)
0 Karma
1 Solution

DalJeanis
Legend

You basically had it, except for one thing. compare these two points...

 ...| table "attachments{}.UniqueID"  ]...

and

 ... UniqueID=1e32fdc2-5519-4e3a-2233-88e49a21e663 ...

If you rename the first fieldname to be the same as the second, then it should work. Test it first with head 1 to save on run time, as below...

index=foo source="Source2" 
    [ search index=bar source="Source1" receiverAddress=test@test.com 
    | dedup "attachments{}.UniqueID" 
    | rename "attachments{}.UniqueID" as UniqueID 
    | head 1 
    | table UniqueID]  
   CreateEvent
| dedup UniqueID
| timechart span=1d count(UniqueID) as "Test"

I'm not familiar with "CreateEvent" - if that is a macro, there should be a tickmark in front of it, and we would have to investigate the code to make sure it would work in that spot with with multiple records. If it is a fieldname, then CreateEvent=* would be more descriptive. If it is a literal, then quotes around it would be better practice.

if it is a macro, then get a second unique id and try this first -

source="Source2" (UniqueID=1e32fdc2-5519-4e3a-2233-88e49a21e663 OR UniqueID=SomeOtherIdThatIsThere) CreateEvent|dedup UniqueID| timechart span=1d count(UniqueID) as "Test"

View solution in original post

0 Karma

DalJeanis
Legend

You basically had it, except for one thing. compare these two points...

 ...| table "attachments{}.UniqueID"  ]...

and

 ... UniqueID=1e32fdc2-5519-4e3a-2233-88e49a21e663 ...

If you rename the first fieldname to be the same as the second, then it should work. Test it first with head 1 to save on run time, as below...

index=foo source="Source2" 
    [ search index=bar source="Source1" receiverAddress=test@test.com 
    | dedup "attachments{}.UniqueID" 
    | rename "attachments{}.UniqueID" as UniqueID 
    | head 1 
    | table UniqueID]  
   CreateEvent
| dedup UniqueID
| timechart span=1d count(UniqueID) as "Test"

I'm not familiar with "CreateEvent" - if that is a macro, there should be a tickmark in front of it, and we would have to investigate the code to make sure it would work in that spot with with multiple records. If it is a fieldname, then CreateEvent=* would be more descriptive. If it is a literal, then quotes around it would be better practice.

if it is a macro, then get a second unique id and try this first -

source="Source2" (UniqueID=1e32fdc2-5519-4e3a-2233-88e49a21e663 OR UniqueID=SomeOtherIdThatIsThere) CreateEvent|dedup UniqueID| timechart span=1d count(UniqueID) as "Test"
0 Karma

kartiksha
Explorer

Hi,

It worked. Thanks for your support DalJeanis. I now need to work on more advanced dashboard so would come back if further queries.

Thanks
Kartik Sharma

DalJeanis
Legend

Great!

So, for my curiosity and everybody's edification, what was CreateEvent?

0 Karma

kartiksha
Explorer

Ahhh... that please ignore. It was a dummy query and I just used one of the keyword from our logs 🙂

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!

Tech Talk Recap | Mastering Threat Hunting

Mastering Threat HuntingDive into the world of threat hunting, exploring the key differences between ...

Observability for AI Applications: Troubleshooting Latency

If you’re working with proprietary company data, you’re probably going to have a locally hosted LLM or many ...

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