This page applies to an earlier version of the AppDynamics App IQ Platform.
For documentation on the latest version, see the 4.4 Documentation.


On this page:

Related pages:

Your Rating:
Results:
PatheticBadOKGoodOutstanding!
55 rates

Page-based snapshots give you a detailed look at an individual page request.  The Summary tab covers general characteristics of the page. For information on the Resource Details tab, see Page Browser Snapshots: Resource Details.

Waterfall Graph

The top of the page snapshot Summary tab displays a waterfall graph of the overall transaction timing for the page. The snapshot is labeled either a Real User Snapshot or a Synthetic Snapshot, based on the origin of the request. 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 (Beta)

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.  A subset of this functionality is available as a generally available Beta for 4.0. See Synthetic - Beta for more information.

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 is displayed, along with a direct link  to the transaction snapshot flow map.

Conversely, the transaction snapshot flow map also contains a link to any related browser snapshot.  For more information, see The Server Side Transaction Snapshot Flow Map for Correlated Business Transactions.

JavaScript Errors

If there are JavaScript errors on the page, they are displayed below the waterfall graph:

You can configure errors to ignore if you are seeing too many errors that are not of interest. See Configure JavaScript and Ajax Error Detection.

(info) When an error occurs in a script that is hosted on a domain other than the domain of the current page, most browsers prevent the JavaScript agent from recording any details of the error.  In such cases the string CROSSDOMAIN is displayed as the Script Origin.

User Data

If you have set up custom user data, it appears in the Details section:


 

The Server Side Transaction Snapshot Flow Map, for Correlated Business Transactions 

Transaction snapshots on the server are triggered when slow or stalled transactions are identified, when a diagnostic session is started, or periodically based on a configured interval. In general, slow, very slow and stalled transactions are more likely to trigger a transaction snapshot on the server than transactions operating within normal range. For more information about when server-side transaction snapshots are captured see Transaction Snapshots

POJO-based business transaction snapshots

Correlating between business transaction snapshots and browser snapshots uses the request GUID and cookies.  In order for the server-side agent to be able to write the cookies, it needs a servlet response object.  In the case where the BT Entry Point is defined by a POJO, this object will not be available unless transaction monitoring has been enabled on the server-side application.

  1. Open the server-side application
  2. In the left navigation bar, select Configuration.
  3. In the Transaction Detection tab, make sure the Transaction Monitoring option for Servlets is Enabled.  

To return to the browser snapshot, click the Browser Snapshot link in the upper right, outlined in red.

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 collection of a given metric. 

See Browser Monitoring Metrics for details about which metrics may not be captured based on browser capabilities.

More on Cookies and Browser Monitoring Data

Browser RUM uses two different kinds of short-lived cookies to help it collect data and correlate events:

  • The ADRUM cookie: written by the JavaScript agent, this cookie contains the referral page URL and some timing information to assist gathering First Byte Time for some browser types.  When the agent loads on the subsequent page, it reads the information and then deletes the cookie.  If there is no agent on that page, the cookie is deleted when the browser is closed.
    For privacy purposes, the URL of the referral page is hashed.
  • The ADRUM_X_Y_Z cookies: written by the server-side agent when the page is served from an instrumented server. These cookies help correlate browser data with related server-side performance data.

If Browser RUM detects that the page is HTTPS, the cookies are HttpsOnly. None of the cookies contain any personally identifiable information (PII).