An important part of Inspector is the ability to visualize performance analysis of a sub-group of transactions and not only for the whole application. Applying a filtering logic to your transactions stream you can create a custom performance report to keep under control specific parts of your application.
Let me show you a real world example.
In a common scenario your application will generate a transactions table like this:
You can see API calls, jobs, and requests generated by frontend navigation.
Our intention is to create a report to analyze only the API section of our app to keep under control if API development is going in the right way or the application will deteriorate their performance over time.
api* in the filter box and click Search:
Your table now contains only api related transactions and performance chart is generated considering only this sub-groups of transactions.
You can save this fitler to reload the report in the future with one click.
Inspector filter is designed for human-entered text and is based on Lucene Query Syntax. Filter queries can be saved and reused with a click so better understand how to search in your transactions stream could give you a lot of free time later.
By default if type some text in the search box it will search all transactions that contains your text in the
Use double quote in case your search query contains more than one word:
text or "my text"
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.
You can also use the wildcard searches in the middle of a term.
Boolean operators allow terms to be combined through logic operators. LOG Engine supports AND, OR, NOT operators (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:
"GET /" GET
"GET /" OR GET
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.
/* NOT POST
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: