Network request snapshots capture detailed information about individual network request instances by your application. They can help you troubleshoot the causes of poorly performing mobile applications.
When Network Request Snapshots are Captured
Mobile RUM starts capturing snapshots when user experience becomes slow, based on how you have configured the thresholds for slow, very slow and stalled. See Configure Mobile Network Request Thresholds.
Periodic snapshots of normal user experience are also captured at least once per minute.
Network Request Snapshot Content
A network request snapshot contains summary data about the individual request as well as any business transactions associated with the request if correlation with an instrumented server side application is available.
The snapshot contains extensive metrics for the request in the Summary data, including:
- User Experience: Normal, Slow, Very Slow, or Stalled.
- Time: when the request was received by the EUM Cloud or EUM Server collector, in UNIX epoch time.
- Mobile Network Request: a link to the network request dashboard for the network request of which this snapshot is an instance. See Network Request Dashboard.
Business Transactions in Network Request Snapshots
When a network request snapshot is associated with one or more business transactions on an instrumented server-side application, the business transactions are listed in the Business Transactions panel in the network request snapshot. You can click the link to see the business transaction dashboard for the associated business transaction.
If transaction snapshots for an associated business transaction were captured at the same time as the network request snapshot, they are linked in the Transaction Snapshots panel of the network request snapshot. If a call graph icon is displayed for a snapshot in the transaction snapshot list, a full or partial call graph is available for that transaction snapshot. This allows you to examine the cause of performance problems on the server side. Click the link to see the associated transaction snapshot.
Transaction snapshots are triggered on the server when slow or stalled business 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.
How to Access Network Request Snapshots from Transaction Snapshots
If a transaction snapshot seen from the server side also has generated a correlated network request snapshot, a mobile snapshot link appears in the top right of the transaction snapshot flow map. Click the link to open the network request snapshot.
Archiving Network Request Snapshots
Normally network request snapshots are purged after two weeks. You can archive a snapshot beyond the normal snapshot lifespan to retain it for future analysis.
To archive a snapshot, click the Archive button in the upper right corner of the snapshot window.
You can view archived snapshots by checking Archived as a view option in the network request snapshots list.
Customers with on-premises controllers can modify the default two-week period by configuring the
event.retention.period property in the Controller Settings section of the Administration console.