Splunk® Enterprise

Search Manual

Field expressions

When you add data, Splunk software extracts pairs of information and saves them as fields. Some fields are common to all events, but others are not. Adding fields to your search term gives you a better chance of matching specific events.

If you are searching web access logs for specific HTTP status errors, instead of searching for "web error 404", you can use fields to search for:

status=404

See Use fields to retrieve events.

Use comparison operators to match field values

You can use comparison operators to match a specific value or a range of field values.

Operator Example Result
= field=foo Multivalued field values that exactly match "foo".
!= field!=foo Multivalued field values that don't exactly match "foo".
< field<x Numerical field values that are less than x.
> field>x Numerical field values that are greater than x.
<= field<=x Numerical field values that are less than and equal to x.
>= field>=x Numerical field values that are greater than and equal to x.

For example, to find events that have a delay field that is greater than 10:

delay > 10

When quotes are required in field expressions

When the value you are searching for contains a breaking character, you must enclose the value in quotation marks.

Examples of breaking characters are spaces, commas, pipes, square brackets, and equals signs. In addition, to search for reserved keywords such as AND, OR, and NOT you must use quotation marks.

Field values that match SPL operators or keywords

There are several field values that match SPL operators or keywords, such as AS, AND, IN, and OR. Here are a few examples:

  • country=IN for India
  • country=AS or state=AS for American Samoa
  • iso=AND for Andorra
  • state=OR for Oregon

To search for field values that match operators or keywords, you must enclose the value in quotation marks. For example: country="IN".

Last modified on 26 May, 2019
Difference between != and NOT   SPL and regular expressions

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.3, 8.1.4, 8.1.5, 8.1.6, 8.1.7, 8.1.8, 8.1.9, 8.1.11, 8.1.13, 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, 8.2.12, 9.0.0, 9.0.1, 9.0.2, 9.0.3, 9.0.4, 9.0.5, 9.0.6, 9.0.7, 9.0.8, 9.0.9, 9.0.10, 9.1.0, 9.1.1, 9.1.2, 9.1.3, 9.1.4, 9.1.5, 9.1.6, 9.1.7, 9.2.0, 9.2.1, 9.2.2, 9.2.3, 9.2.4, 9.3.0, 9.3.1, 9.3.2, 9.4.0, 8.1.10, 8.1.12, 8.1.14, 8.1.2


Was this topic useful?







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