Dropped Requests SLE

What Does the Dropped Requests SLE Measure?

Juniper Mist monitors the instances when dropped location requests reduced location accuracy.

You can click the Settings button to set the number of pending requests to allow as the SLE success threshold. Pending requests are used as a likely indicator of requests that will be dropped in the future.

Note:

The Pending Requests classifier uses the threshold that you set here. The other classifiers act on a pass/fail basing, counting any incidents that result in dropped requests.

Classifiers for Excessive Dropped Requests

When the number of dropped requests exceeds the threshold, Juniper Mist classifies the issues as follows.

• Reconnects—The app client briefly lost Internet connectivity and made attempts at reconnecting (successful or not).

• Offline—The app client went offline while using the app. The device might have had poor Wi-Fi reception, poor cellular reception, or connectivity problems. The user might have switched to airplane mode or turned off Wi-Fi.

• Not Uniform Requests—The app client sent some location requests at a faster or slower rate than expected, causing possible synchronization issues that affected location accuracy. (The app relies on uniform requests for proper location accuracy.)

• Dropped by Network—The app client's location requests were dropped while going through the network.

• Client Request Timeout—The app client's requests timed out.

• Cellular—The app client was using a cellular data connection.

• WiFi—The app client was using a Wi-Fi connection.

• Pending Requests—The number of pending requests exceeded the SLE threshold.

Example

• Success Rate—On the left, you see that the Dropped Requests threshold was met only 6 percent of the time.

• Timeline—In the middle, you can drag your mouse to explore this SLE over time. This example shows an 11 percent success rate at the selected time. To adjust the scope of the timeline, use the timeline drop-down list at the top of the Monitor page. For example, set the timeline to Today, Yesterday, This Week, or a custom date range.

• Classifiers—On the right, you see a high-level root cause analysis for the dropped requests. Many issues were attributed to Pending Requests (44 percent), WiFi (23 percent), and Client Request Timeout (21 percent). Other issues were attributed to Dropped by Network (11 percent), Not Uniform Requests (1 percent), and Reconnects (less than 1 percent). No issues (0 percent) were attributed to Cellular or Offline.

Note:

You can click the Values button to show numbers instead of the success rate and classifier percentages. On the left, you see the number of dropped requests for the entire time period. The timeline shows the number of dropped requests at the selected time. On the right, you see the number of droppsed requests for each classifier.