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.
Explore our filtering syntax.