You can search and filter log events in the Explore Logs page.

To find only events that contain the specified keywords, enter any complete keywords, globs, or phrases in the search text box and click Search.

You can specify the time range on either the Dashboards or Explore Logs pages in the web user interface. Time ranges are inclusive when filtering.

You can search for log events that match certain values of specific fields. Using quoted text in the main search field matches exact phrases. Entering space in the main search field is a logical AND operator. Search uses only full tokens. For example, searching for "err" does not find "error" as a match.

Note: The field name for an ingested event must begin only with a letter or an underscore character and contain only letters, digits, or the underscore character.

You can enter the field search criteria, or filters, by using the drop-down menus and the text box above the list of log events.

Within a single-row filter, you can use comma-separated values to list OR filters. For example, select hostname contains and type, The search returns events with the host name or

The text contains filter treats each comma-separated value as a complete keyword.

Queries with fields using the internal query language syntax names, for example, from or in, are not able to be processed and should not be used.

You can combine multiple field filters by creating a filter row for each field. You can toggle the operator that is applied to multiple-row filters .

  • To apply the AND operator, select all.
  • To apply the OR operator, select any.
Note: Regardless of the toggle value, the operator for comma-separated values within a single filter row is OR, except when you use the _index field. For the _index field, the operator is AND.

You can use globs in search terms. For example, vm* or vmw?re.

  • For 0 or more characters, use *.
  • For one character, use ?.
Note: Globs cannot be used as the first character of a search term. For example, you can use 192.168.0.*, but you cannot use *.168.0.0 in your filtering queries.