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!

Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Persistent Queue at TcpOut — One of Splunk's Most Practical Features

Splunk introduced persistent queueing at the tcpout layer as one of the most practical resilience features in ...

Skip the Awkward Silence: Have a .conf-ersation at .conf26

Picture this. You arrive at .conf26 already having your socializing and networking plans mapped out. No ...

Rethinking Zero Trust: From Product Purchases to Logical Control Evidence

Implementing Zero Trust (ZT) across complex environments often falters at the very beginning due to a ...