Prevents subsequent commands from being executed on remote peers.
Tells Splunk to run subsequent commands, that is all commands following this, locally and not on a remote peer(s). Another way to think of it is that the localop command forces subsequent commands to be part of the reduce step of the mapreduce process.
Example 1: The iplocation command in this case will never be run on remote peers. All events from remote peers from the initial search for the terms FOO and BAR will be forwarded to the search head where the iplocation command will be run.
FOO BAR | localop | iplocation
Have questions? Visit Splunk Answers and see what questions and answers the Splunk community has using the localop command.
This documentation applies to the following versions of Splunk: 4.1 , 4.1.1 , 4.1.2 , 4.1.3 , 4.1.4 , 4.1.5 , 4.1.6 , 4.1.7 , 4.1.8 , 4.2 , 4.2.1 , 4.2.2 , 4.2.3 , 4.2.4 , 4.2.5 , 4.3 , 4.3.1 , 4.3.2 , 4.3.3 , 4.3.4 , 4.3.5 , 4.3.6 , 5.0 , 5.0.1 , 5.0.2