Page-based snapshots give you a detailed look at individual page requests. The Summary tab covers the general characteristics of the page. For information on the Resource Details tab, see Page Browser Snapshots - Resource Details.
The top of the page snapshot Summary tab displays a waterfall graph of the overall transaction timing for the page. You can hover over each of the metrics to see a popup definition for that metric.
For more information on what these metrics mean, see Browser RUM Metrics. Additional details associated with the snapshot, including any Related Snapshots and any custom User Data, are displayed as a table below the graph.
Generate a Synthetic Snapshot - SaaS Only
Synthetic snapshots use geographically distributed agents to create snapshots of web page download performance without the idiosyncratic and potentially skewing effects of real user last-mile performance. You can use this button to create an on-demand synthetic snapshot to compare with a problematic RUM snapshot.
Correlated Transaction Snapshots and Business Transactions
If server-side correlation has been set up, a link to any related business transaction is shown:
Clicking the link takes you to the flow map for that business transaction on the server side.
If the business transaction created a transaction snapshot, links to the business transaction, tier, and node flow maps are displayed, along with a direct linkto the transaction snapshot flow map. Cross-app correlation is supported.
In this case, the transaction snapshot also has a link back to the browser snapshot.
CROSSDOMAIN is displayed as the Script Origin.
If you have set up custom user data, it appears in the Details section:
Unknown Metrics in Browser Snapshots
Browser RUM captures metrics using your end-users' web browsers. Occasionally, you may see Unknown data reported for one or metrics in a browser snapshot. This occurs on older or less sophisticated browsers that do not support the collection of a given metric.
See Browser Monitoring Metrics for details about which metrics may not be captured based on browser capabilities.