Network Requests List
The Network Requests list shows all the network requests types from your instrumented mobile application, along with their key performance indicators.
Network Requests List Organization
TheNetwork Requestslist is a table that displays aggregated metrics for current requests, with one row for each request type. The columns display the name of the network request and the aggregated metrics associated with it. See Mobile RUM Metrics for descriptions of these metrics.
Click a column header to sort the list based on the column's metric. For example, if you want to sort by the slowest requests, click the Network Request Time (ms) column header. You can toggle the column to switch between ascending and descending order. Use View Options to configure the table. Check With Load if you want to show only network request types that have experienced active load, that is, those for which there were one or more measured network requests over the selected time period.
To view a network request dashboard:
- Select the network request type in the list.
- Click Details or double-click the network request.
- Exclude Request(s): Use this option to direct Splunk AppDynamics to ignore the selected request(s) and stop reporting metrics for them.You can use the View Excluded Requests option to see requests that have been excluded and then you can "un-exclude" them.
- Rename Request: Use this option to rename one selected request in the Splunk AppDynamics console.
- Delete Request(s): Use this option to remove the request(s) from the list. If Splunk AppDynamics discovers a deleted request again it will reappear in the list. To prevent it from re-appearing, use Exclude Request(s).
Network Request Dashboard
Each network request type has its own dashboard that graphically displays key performance indicators for that type over the selected time range. To select the time range, use the general time range dropdown at the top right of the UI.
Network Request Dashboard Organization
The Network Request Dashboard displays summary key network request metrics for the time selected. To see any particular metric in the metric browser, click the metric value (in link blue).
The trend graphs for the key performance indicators are:
- Network Request Time: Average times in milliseconds.
- Server Request Time: The time taken by the request to reach the server from the mobile device.
- Server Response Time: The time taken by the response to reach the mobile device from the server.
- JSON Parsing Time: The time taken by the mobile device for parsing the JSON response. SeeConfigure the Agent to Record the JSON Parsing Time.
- Total Server Time: Displayed only If the mobile request is correlated with a server-side application.The total server time is the interval between the time that the server-side application receives the network request to the time that it finishes processing the request. Use this graph to determine, on average, how much time is spent on the network versus how much time is spent on the server to process the user's request.
- Load: Total Requests and Requests per Minute.
- Errors: Network Errors and HTTP Errors in total and per minute.
- Related Business Transactions: If the request is correlated with a server-side application, the dashboard lists business transactions associated with the request below the performance metrics. You can click the link to a related business transaction to see its business transaction dashboard.If transaction snapshots were taken at the same time as the network request, the dashboard lists the transaction snapshots below the business transactions. SeeTroubleshoot Business Transaction Performance with Transaction Snapshots.
You can hover over any data point on any of the trend graphs to see the metric for a precise point:
Configure the Agent to Record the JSON Parsing Time
When you instrument the agent, configure the agent with the following code to record the JSON parsing time:
NSString *urlString = url.absoluteString // During auto instrumentation Splunk AppDynamics tracks the url string using url.obsoluteString. Therefore, specify the same value in the below code to correlate with the network requests.
[ADEumInstrumentation startTimerWithName: urlString];
// Json parsing logic.
[ADEumInstrumentation stopTimerWithName:urlString];