Filters & Display
You can filter the information displayed on the Performance page by searching or using page-level display filters.
The page displays a view of transactions, but you can click the “View Trends” button to view trends information. The different ways you can filter and set the display of transactions is described fully on this page. To learn more about viewing transactions by trend, see our Trends View documentation.
Each tab in Performance displays an automatically selected set of widgets and table columns based on the platform of your
When you select "All Transactions", the table includes all transactions across any projects and period you have selected.
Web Vitals includes frontend pageload transactions. The transactions are automatically filtered to only include
transaction.op:pageload. This generally corresponds to all browser page transitions that are the first load of a page. It also includes performance information from the beginning of the load itself, as well as the performance of the SPA frameworks being loaded, such as React or Vue (if available).
"Frontend" includes all frontend transactions, without a specific focus on Web Vitals. This generally corresponds to page transitions handled internally in SPA frameworks, such as React or Vue. Note that if you've selected a backend
"Backend" puts an emphasis on duration, throughput, failure rate, and Apdex. Note that if you've selected a frontend
"Mobile" puts an emphasis on Mobile Vitals. Note that if you've selected a non-mobile
Rather than searching for transactions by matching event properties, the search bar on the Performance page filters by transaction name only. You can search for specific transaction names or use wildcards, which can take the place of one or more characters in a search term (e.g.,
When you begin typing, a list of transaction names that match your search appear. There are two ways to interact with the search results:
- Clicking on a transaction name will apply a filter on the Performance page to only display transaction data for the selected transaction.
- Clicking the upwards arrow icon on a search result will take you to that transaction's summary page.
In the transaction summary, the search bar operates similarly to the one in the Discover Query Builder. For example, you can refine your transaction search to a specific release by using
release: as a key field and assigning the version as a value.
Widgets offer visualizations that you can change to best match your workflow.
In the first row, there are time series and distribution graphs of common metrics for the selected
In the second row, there are actionable widgets that can show you areas of concern in your application, such as Most Regressed Transactions or Most Recurring Issues. Below these widgets, there are lists of transactions, which you can click to see additional context. Transactions shown in these lists can be temporarily removed from the view by clicking the 'X' beside the transaction name.
Each widget has a menu in the top right where can you change the widget shown. Your changes will be persisted locally either for the session or until application storage is cleared. After that, the default set of widgets is displayed.
- Transactions Per Minute (TPM)
- Failure Rate
- p50 Duration
- p75 Duration
- p95 Duration
- p99 Duration
- User Misery
- Most Improved
- Most Regressed
- Most Related Issues
- Most Slow Frames
- Most Frozen Frames
- Most Time-Consuming Queries
- Best Page Opportunities
- Performance Score
- Slow HTTP Ops
- Slow DB Ops
- Slow Browser Ops
- Slow Resource Ops
The table of transactions provides a list of the most frequent transactions based on the current page filters and display options. By default, the table is sorted by transactions per minute, with the most frequent transactions displayed first. The table may be filtered further based on the page and search condition filters. The Display Filter controls what displays in the table columns, such as:
If you have transactions you frequently return to, you can mark them as a key transaction for any of your teams by clicking the star in the corresponding row. Each team can mark up to 100 transactions as a key transaction. These key transactions are shared with all members of the team ensuring the most important information is surfaced to the top of the list. You can also mark a transaction as a key transaction in its corresponding summary view.