In most cases, a user's interaction with your app is not limited to one action in one screen view. Sessions allow you to track your users' interactions across time, as they navigate an entire session with your app.
Sessions begin when a user starts using your application and ends after a configurable period of user inactivity. Using Mobile Sessions you can analyze sessionized results from all requests, as stored in the AppDynamics Events Service.
As in Network Request Analyze, the main Sessions screen is made up of two tabs:
You can also view detailed information about each session in the Session Details dialog.
The Records tab lets you scan individual sessions and allows you to filter and sort to get exactly the data in which you are interested.
Click View Details or double click an item to see the information for a specific session. The sequence of screen views for the session is shown on the left side of the screen. Select a specific screen view to see details. If your backend is also instrumented with AppDynamics, you can see any correlated business transaction information by clicking the Correlation tab.
When an app crashes and is restarted before the configured inactivity period expires, the subsequent activity is added to the current session, as though it were a continuous session. In the Session Details dialog, an app crash in a session is indicated by a screen view shown in red font. In the screenshot above, you can see that the app crashed by the screen view ConfirmationPane and then was restarted during the same session by the presence of the subsequent screen view Confirmation Pane.
If you select the screen that had the crash and click the crash event on the timeline, you can see an overview of the crash details in a dialog as shown below.
The Charts page provides you with a set of predefined widgets that offer visualizations of the data set you have created. As with the Charts pages of the other Analyze/Session features of the UI, you can delete, re-add, resize, and drag-and-drop to move all of the widgets.