Filters & Display

You can filter the information displayed on the Performance page by searching or using page-level display filters.

Transaction and Trend Views

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.

Tabs

Each tab in Performance displays an automatically selected set of widgets and table columns based on the platform of your project. For example, a JavaScript project displays the "Web Vitals" tab by default. Each tab and its metrics are explained below.

Performance homepage with Web Vitals tab selected.

All Transactions

When you select "All Transactions", the table includes all transactions across any projects and period you have selected.

Web Vitals

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

"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 project, this mode also displays backend transactions.

Backend

"Backend" puts an emphasis on duration, throughput, failure rate, and Apdex. Note that if you've selected a frontend project, this mode also displays all frontend transactions.

Mobile

"Mobile" puts an emphasis on Mobile Vitals. Note that if you've selected a non-mobile project, this mode also displays all of those transactions.

Search Condition Filters

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

Widgets offer visualizations that you can change to best match your workflow.

Performance homepage with Web Vitals widgets.

In the first row, there are time series and distribution graphs of common metrics for the selected project type (frontend or backend), such as User Misery or Failure Rate. You can compare these side-by-side to find any correlations.

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.

Basic Widgets

Actionable Widgets

Transaction Table

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:

Starring Key Transactions

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.

Help improve this content
Our documentation is open source and available on GitHub. Your contributions are welcome, whether fixing a typo (drat!) to suggesting an update ("yeah, this would be better").