Filtering Syntax

Apply filters with an intuitive, human-friendly search.

Inspector filter is designed for human-entered text. Filter queries can be saved and reused with a click so understand how to search in your transactions stream could give you a lot of free time later.

Why use filters

You can visualize performance statistics of a sub-part of your system and not only for the whole application. Applying a filtering logic to your Monitoring dashboard you can create a custom view to keep specific parts of your app under control.

Let me show you a real world example.

Suppose to have a transactions list with jobs, http requests, and commands executed by your application.

We want isolate the "console commands" to understand if the background work done by your application is going in the right way.

Type "artisan" in the filter box and push enter.

Simple Text

By default the text used as query will filter the transactions list by name.

Remeber to use double quotes:

"my text query"


Inspector supports single and multiple character wildcard searches within single terms (not within phrase queries).

To perform a single character wildcard search use the "?" symbol.


To perform a multiple character wildcard search use the "*" symbol.



Boolean operators allow terms to be combined through logic operators. AND, OR, NOT operators are supported (Note: operators must be ALL CAPS).


The OR operator is the default conjunction operator. This means that if there is no Boolean operator between two terms, the OR operator is used.

To search for transactions that contain either "GET /" or just "GET" use the query:





The AND operator matches records where both terms exist in the event fields.

GET AND "/api"


The NOT operator excludes documents that contain the term after NOT.



You can filter both numeric and string value using range:

# Filter by transaction duration
duration:[800 TO 900]

# Filter by transaction memory_peak
memory_peak:[40 TO 50]

Escaping Special Characters

You need to consider special characters all the items that could be interfere with syntax:

  • :

  • *

  • ?

  • (

  • )

To escape these character use the \ before the character. For example to search for route:list use the query:


Last updated