Splunk Cloud

Search Reference

Download manual as PDF

Download topic as PDF

makeresults

Description

Generates the specified number of search results.

If you do not specify any of the optional arguments, this command runs on the local machine and generates one result with only the _time field.

Syntax

| makeresults [<count>] [<annotate>] [<splunk-server>] [<splunk-server-group>...]

Required arguments

None.

Optional arguments

<count>
Syntax: count=<num>
Description: The number of results to generate. If you do not specify the annotate argument, the results have only the _time field.
Default: 1
<annotate>
Syntax: annotate=<bool>
Description: If annotate=true, generates results with the fields shown in the table below.
If annotate=false, generates results with only the _time field.
Default: false
Fields generated with annotate=true
Field Value
_raw None.
_time Date and time that you run the makeresults command.
host None.
source None.
sourcetype None.
splunk_server The name of the server that the makeresults command is run on.
splunk_server_group None.
You can use these fields to compute aggregate statistics.
<splunk-server>
Syntax: splunk_server=<string>
Description: Use to generate results on one specific server. Use 'local' to refer to the search head.
Default: local. See the Usage section.
<splunk-server-group>
Syntax: (splunk_server_group=<string>)...
Description: Use to generate results on a specific server group or groups. You can specify more than one <splunk_server_group>.
Default: none. See the Usage section.

Usage

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

You can use this command with the eval command to generate an empty result for the eval command to operate on. See the Examples section.

Order-sensitive processors might fail if the internal _time field is absent.

Specifying server and server groups

If you use Splunk Cloud, omit any server or server group argument.

If you are using Splunk Enterprise, by default results are generated only on the originating search head, which is equivalent to specifying splunk_server=local. If you provide a specific splunk_server or splunk_server_group, then the number of results you specify with the count argument are generated on the all servers or server groups that you specify.

If you specify a server, the results are generated for that server, regardless of the server group that the server is associated with.

If you specify a count of 5 and you target 3 servers, then you will generate 15 total results. If annotate=true, the names for each server appear in the splunk_server column. This column will show that each server produced 5 results.

Examples

1. Create a result as an input into the eval command

Sometimes you want to use the eval command as the first command in a search. However, the eval command expects events as inputs. You can create a dummy event at the beginning of a search by using the makeresults command. You can then use the eval command in your search.

| makeresults | eval newfield="avalue"

2. Determine if the modified time of an event is greater than the relative time

For events with the field scheduled_time that is in Unix Epoch time, determine if the scheduled time is greater than the relative time. The relative time is 1 minute before now. This search uses a subsearch that starts with the makeresults command.

index=_internal sourcetype=scheduler ( scheduled_time > [ makeresults | eval it=relative_time(now(), "-m") | return $it ] )

See also

gentimes

Answers

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

PREVIOUS
makemv
  NEXT
map

This documentation applies to the following versions of Splunk Cloud: 6.6.3, 7.0.3, 7.0.0, 7.0.2


Comments

Heads up - in Splunk Enteprise 6.5, if you're using "makeresults" and you click the "learn more" link for make results, it drops you at the Admin Manual homepage. It should instead send them to this docs page.

Sideview
November 1, 2016

Woodcock - I have added gentimes to the See also section. I did not add makeresults, as that would create a circular link.

Lstewart splunk, Splunker
July 19, 2016

This should reference "makeresults" in the "see also" section.

Woodcock
July 18, 2016

This should reference "gentimes" in the "see also" section.

Woodcock
July 18, 2016

Woodcock and Mueller - I updated the examples based on your comments and input from one of our lead engineers (CPride).

Lstewart splunk, Splunker
December 15, 2015

Your first example is missing a leading pipe ("|") character.

Woodcock
December 5, 2015

If someone confuses the greater than for an output redirect, switching to less than will make them confuse it for an input redirect.

Besides, use _index_earliest=-m instead ;p

Martin mueller
December 5, 2015

The last example makes it appear that the greater-than sign is a piping character I would use parentheses and switch to lesser-than to avoid this confusion:

index=_internal (_indextime < [makeresults | eval it=now()-60 | return $it])

Woodcock
December 4, 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