Search Reference

 


sirare

sirare

Use the summary indexing reporting commands (sichart, sitimechart, sistats, sitop, and sirare) to define the search that will populate the summary index. If you use these commands, you can use the same search string for the search that you eventually run on the summary index, with the exception that you use regular reporting commands (chart, timechart, stats, top, and rare, respectively) in the latter search.

Read more about the summary indexing reporting commands in "Use summary indexing for increased reporting efficiency" topic of the Knowledge Manager Manual.

Synopsis

Summary indexing version of the rare command.

Syntax

sirare rare_syntax

Arguments

Refer to the rare command syntax.

Description

Summary indexing friendly versions of rare command, using the same syntax. Does not require explicitly knowing what statistics are necessary to store to the summary index in order to generate a report.

Does require the rare command used to process this data have the exact same arguments as were used with the sirare command to generate the data.

Examples

Example 1: Compute the necessary information to later do 'rare foo bar' on summary indexed results.

... | sirare foo bar

See also

collect, overlap, sichart, sistats, sitimechart, sitop

Answers

Have questions? Visit Splunk Answers and see what questions and answers the Splunk community has using the sirare 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 , 5.0.3 View the Article History for its revisions.


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

Was this documentation topic helpful?

If you'd like to hear back from us, please provide your email address:

We'd love to hear what you think about this topic or the documentation as a whole. Feedback you enter here will be delivered to the documentation team.

Feedback submitted, thanks!