Define search macros in Settings
Search macros are reusable chunks of Search Processing Language (SPL) that you can insert into other searches. Search macros can be any part of a search, such as an eval statement or search term, and do not need to be a complete command. You can also specify whether the macro field takes any arguments.
- See Insert search macros into search strings.
- See Design a search macro definition.
- (Optional) If your search macros require the search writer to provide argument variables, you can design validation expressions that tell the search writer when invalid arguments have been submitted. See Validate search macro arguments.
- Select Settings > Advanced Search > Search macros.
- Click New to create a search macro.
- (Optional) Check the Destination app and verify that it is set to the app that you want to restrict your search macro to. Select a different app from the Destination app list if you want to restrict your search macro to a different app.
- Enter a unique Name for the search macro.
If your search macro includes an argument, append the number of arguments to the name. For example, if your search macro
mymacroincludes two arguments, name it
- In Definition, enter the search string that the macro expands to when you reference it in another search.
- (Optional) Click Use eval-based definition? to indicate that the Definition value is an
evalexpression that returns a string that the search macro expands to.
- (Optional) Enter any Arguments for your search macro. This is a comma-delimited string of argument names. Argument names may only contain alphanumeric characters (a-Z, A-Z, 0-9), underscores, and dashes. The string cannot contain repetitions of argument names.
- (Optional) Enter a Validation expression that verifies whether the argument values used to invoke the search macro are acceptable. The validation expression is an
evalexpression that evaluates to a Boolean or string value.
- (Optional) Enter a Validation error message if you defined a validation expression. This message appears when the argument values that invoke the search macro fail the validation expression.
- Click Save to save your search macro.
Design a search macro definition
The fundamental part of a search macro is its definition, which is the SPL chunk that the macro expands to when you reference it in another search.
If your search macro definition has variables, the macro user must input the variables into the definition as tokens with dollar signs on either side of them. For example,
$arg1$ might be the first argument in a search macro definition.
The SPL in a search macro definition must comply with the syntax requirements of the search command that uses it. For example,
eval command syntax requires that any literal string in the expression is surrounded by double quotation marks. When using a search macro with the
eval command, a literal string in the search macro definition must be surrounded by double quotation marks.
Pipe characters and generating commands in macro definitions
When you use generating commands such as
tstats in searches, put them at the start of the search, with a leading pipe character.
If you want your search macro to use a generating command, remove the leading pipe character from the macro definition. Place it at the start of the search string that you are inserting the search macro into, in front of the search macro reference.
For example, you have a search macro named
mygeneratingmacro that has the following definition:
tstats latest(_time) as latest where index!=filemon by index host source sourcetype
The definition of
mygeneratingmacro begins with the generating command
tstats. Instead of preceding
tstats with a pipe character in the macro definition, you put the pipe character in the search string, before the search macro reference. For example:
Validate search macro arguments
When you define a search macro that includes arguments that the user must enter, you can define a Validation expression that determines whether the arguments supplied by the user are valid. You can define a Validation error message that appears when search macro arguments fail validation.
The validation expression must be an
eval expression that evaluates to a Boolean or a string. If the validation expression is boolean, validation succeeds when the validation expression returns
true. If it returns
false, or returns null, validation fails.
If the validation expression is not Boolean, validation succeeds when the validation expression returns null. If it returns a string, validation fails.
For more information, see the following resources.
- Search macro examples
- macros.conf in the Admin Manual. The
macros.confconfiguration file is where Splunk software stores search macro definitions.
- Generating commands in the Search Reference.
Use search macros in searches
Search macro examples
This documentation applies to the following versions of Splunk® Enterprise: 7.0.0, 7.0.1, 7.0.2, 7.0.3, 7.0.4, 7.0.5, 7.0.6, 7.0.7, 7.0.8, 7.0.9, 7.0.10, 7.0.11, 7.0.13, 7.1.0, 7.1.1, 7.1.2, 7.1.3, 7.1.4, 7.1.5, 7.1.6, 7.1.7, 7.1.8, 7.1.9, 7.1.10, 7.2.0, 7.2.1, 7.2.2, 7.2.3, 7.2.4, 7.2.5, 7.2.6, 7.2.7, 7.2.8, 7.2.9, 7.2.10, 7.3.0, 7.3.1, 7.3.2, 7.3.3, 7.3.4, 7.3.5, 7.3.6, 7.3.7, 7.3.8, 7.3.9, 8.0.0, 8.0.1, 8.0.2, 8.0.3, 8.0.4, 8.0.5, 8.0.6, 8.0.7, 8.0.8, 8.0.9, 8.0.10, 8.1.0, 8.1.1, 8.1.2, 8.1.3, 8.1.4, 8.1.5, 8.1.6, 8.1.7, 8.1.8, 8.1.9, 8.1.10, 8.1.11, 8.1.12, 8.1.13, 8.1.14, 8.2.0, 8.2.1, 8.2.2, 8.2.3, 8.2.4, 8.2.5, 8.2.6, 8.2.7, 8.2.8, 8.2.9, 8.2.10, 8.2.11, 9.0.0, 9.0.1, 9.0.2, 9.0.3, 9.0.4, 9.0.5
Feedback submitted, thanks!