Splunk Search

Does multisearch suffer from subsearch limits?

marcusnilssonmr
Path Finder
 
Tags (1)

acharlieh
Influencer

That is a very good question! So let's figure it out. First create a test index in your splunk instance. Next we can use gentimes to create 259,200 events (number of seconds in 3 days) and use a summary indexing command collect to populate that index like so:

| gentimes increment=1s start=-3 end=0 | eval _raw=strftime(starttime,"%FT%TZ").", one=1" | fields + _raw | collect index=test

Now we can use multisearch to test our theory. If we are subject to the subsearch maxout limit of 10,000 results, then the following search should only pull back 30,000 events:

| multisearch [search index=test earliest=-7d@d] [search index=test earliest=-7d@d] [search index=test earliest=-7d@d]

And we pull back 777,600 events. Thus multisearch must not be subject to the standard subsearch limit.

cleavesn
Engager

Thank you for the note!

Get Updates on the Splunk Community!

Building Reliable Asset and Identity Frameworks in Splunk ES

 Accurate asset and identity resolution is the backbone of security operations. Without it, alerts are ...

Cloud Monitoring Console - Unlocking Greater Visibility in SVC Usage Reporting

For Splunk Cloud customers, understanding and optimizing Splunk Virtual Compute (SVC) usage and resource ...

Automatic Discovery Part 3: Practical Use Cases

If you’ve enabled Automatic Discovery in your install of the Splunk Distribution of the OpenTelemetry ...