Splunk Cloud

Search Reference

Download manual as PDF

Download topic as PDF



Run multiple searches at the same time.

The multisearch command is a generating command that executes multiple streaming searches at the same time. It requires at least two subsearches and allows only streaming operations in each subsearch. Examples of streaming searches include searches with the following commands: search, eval, where, fields, and rex. For more information, see Types of searches in the Search Manual.


| multisearch <subsearch1> <subsearch2> <subsearch3> ...

Required arguments

Syntax: "["search <logical-expression>"]"
Description: At least two streaming searches. See the search command for detailed information about the valid arguments for the <logical-expression>.
To learn more, see About subsearches in the Search Manual.


The multisearch command is a generating command and should be the first command in the search. Generating commands use a leading pipe character.

Subsearch processing and limitations

With the multisearch command, the events from each subsearch are interleaved. Therefore the multisearch command is not restricted by the subsearch limitations.

Unlike the append command, the multisearch command does not run the subsearch to completion first. The following subsearch example with the append command is not the same as using the multisearch command.

index=a | eval type = "foo" | append [search index=b | eval mytype = "bar"]


Example 1:

Search for events from both index a and b. Use the eval command to add different fields to each set of results.

| multisearch [search index=a | eval type = "foo"] [search index=b | eval mytype = "bar"]

See also

append, join


Have questions? Visit Splunk Answers and see what questions and answers the Splunk community has using the multisearch command.


This documentation applies to the following versions of Splunk Cloud: 6.5.0, 6.5.1, 6.5.1612, 6.6.0, 6.6.1, 6.6.3


No, these are not the same. In multisearch you will get events interleaved. Unlike append, it doesn't run the subsearch to completion first. So it is not subject to the subsearch limitations.

Lstewart splunk, Splunker
April 12, 2016

I assume that your example is exactly the same as this:

index=a | eval type = "foo" | append [search index=b | eval mytype = "bar"]

If so (or if not), this would be good to note.

ALSO, I assume this is subject to all the subsearch-limits, right? This, too, should be mentioned.

April 10, 2016

Was this documentation topic helpful?

Enter your email address, and someone from the documentation team will respond to you:

Please provide your comments here. Ask a question or make a suggestion.

You must be logged into splunk.com in order to post comments. Log in now.

Please try to keep this discussion focused on the content covered in this documentation topic. If you have a more general question about Splunk functionality or are experiencing a difficulty with Splunk, consider posting a question to Splunkbase Answers.

0 out of 1000 Characters