Splunk Cloud

Search Reference

Download manual as PDF

Download topic as PDF



Appends the result of the subpipeline to the search results. Unlike a subsearch, the subpipeline is not run first. The subpipeline is run when the search reaches the appendpipe command. The appendpipe command is used to append the output of transforming commands, such as chart, timechart, stats, and top.


appendpipe [run_in_preview=<bool>] [<subpipeline>]

Optional Arguments

Syntax: run_in_preview=<bool>
Description: Specifies whether or not display the impact of the appendpipe command in the preview. When set to FALSE, the search runs and the preview shows the results as if the appendpipe command is not part of the search. However, when the search finishes, the results include the impact of the appendpipe command.
Default: True
Syntax: <subpipeline>
Description: A list of commands that are applied to the search results from the commands that occur in the search before the appendpipe command.


The appendpipe command can be useful because it provides a summary, total, or otherwise descriptive row of the entire dataset when you are constructing a table or chart. This command is also useful when you need the original results for additional calculations.


Example 1:

Append subtotals for each action across all users.

index=_audit | stats count by action user | appendpipe [stats sum(count) as count by action | eval user = "TOTAL - ALL USERS"] | sort action

The results appear on the Statistics tab and look something like this:

action user count
accelerate_search admin 209
accelerate_search buttercup 345
accelerate_search can-delete 6
accelerate_search TOTAL - ALL USERS 560
add n/a 1
change_authentication admin 50
change_authentication buttercup 9
change_authentication can-delete 24
change_authentication TOTAL - ALL USERS 83

See also

append, appendcols, join, set


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


This documentation applies to the following versions of Splunk Cloud: 6.6.3, 7.0.2, 7.0.3, 7.0.0, 7.0.5, 7.0.8, 7.0.11, 7.1.3, 7.1.6, 7.2.3, 7.2.4, 7.2.6, 7.2.7, 7.2.8, 7.2.9, 8.0.0, 8.0.1


Hello lalleman
Thank you for your comment. I spoke with one of our lead developers. As a result of your question, I have filed a bug to investigate this issues of using map with appendpipe. He also mentioned that the map command is not particularly scalable. Please post your question on Splunk Answers or on Slack Chat. We have a great customer community who are particularly good at helping others with their specific questions.Here are the links to both Answers and Chat:

Lstewart splunk, Splunker
February 2, 2016

Are there any notable distinctions between a [<subpipeline>] and a [<subsearch>]? Clearly the first search command within the subpipeline is not a generating search command (as it would be in a subsearch), but other than that, are there any restrictions? In particular, I'm running into trouble getting the "map" command to work within an appendpipe and can't determine if that's a known limitation, intentional restriction, or just a bug.

January 28, 2016

Woodcock, thanks for noticing that. I have added a more complete description to the 'run_in_preview' argument.

Lstewart splunk, Splunker
December 4, 2015

There is no description to tell us what "run_in_preview" does.

October 16, 2015

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