Application Performance Analytics

The Application Performance Analytics insight is used to understand passive latency of SaaS and Real time applications such as Microsoft Teams and Skype with respect to its geographical location based on the closest peer at the city, state, country, or application level. You can view the analytics for the previous 24 hours or seven days.

Geo location based peers are formed with at least 10 applications at a given level. At the city level, if the number of applications is at least 10, city level peers are formed; otherwise, state level applications are checked; if state level applications are at least 10, state level peers are formed; otherwise, country level applications are checked; and if country level applications are more than 10, country level peers are formed; otherwise, application level peers are formed without checking the application count.

After the peers are formed, the application's 90th percentile latency over a one-day period is first checked at the most granular level, which is the city level; if city level peers are not present, state level peers are checked; if state level peers are also not present, country level peers are checked; and finally, if no peers are available, application level peers are compared.

Listed below are the guard rails:

  • Real Time Application Latency Guard Rail

    • Good – If the latency is less than 100 ms.

    • Fair- If the latency is greater than 100 ms and less than 200 ms.

    • Poor - If the latency is greater than 200 ms.

  • SaaS Application Latency Guard Rail

    • Good – If the latency is less than 200 ms.

    • Fair- If the latency is greater than 200 ms and less than 400 ms.

    • Poor - If the latency is greater than 400 ms.

To access the Application Performance Analytics insight, complete the following steps:

  1. Access the Insights page. For more information, see Accessing Insights Page.

  2. Click the Application Performance Analytics tab.

    The Real Time Application Flows for SaaS Applications for last seven days is displayed.

    Click the 24 Hours tab to view the last 24 hours data. You can use the application drop-down to switch between SaaS Applications and Real Time Applications.

You can view the following metrics:

  • Actions—This tile recommends you to consult your Internet Service Provider (ISP) about potential WAN communication concerns. Click the View button to view the Impacted Applications And Root Causes Analysis window.

  • Real Time Applications Flows—The graph displays the number of application flows in the y-axis and the application latency in the x-axis. You can also hover over the graph to view the actual values.

  • Impacted Applications—The graph displays how application latency (green line) compares to application peer latency (amber line) and guard rails (gray line). The y-axis displays the latency in milliseconds, while the x-axis displays the time period. To view a specific application's latency, select it from the drop-down list. You can also hover over the graph to see the actual latency values.

Figure 1: Impacted Applications And Root Cause Analysis Window

In the Impacted Applications And Root Causes Analysis window, you can view the following details:

Table 1: Impacted Applications And Root Causes Analysis Window Parameters

Parameter

Description

Applications

Displays the name of the application.

App Latency

Displays the average of 90th percentile of application latency for the impacted duration.

Top Apps Latency on Gateway

Displays the Gateway's latency as well as the average 90th percentile of all apps for the affected time period.

Average App Peer latency

Displays the average app peer latency of an application for the impacted duration.

Peer Comparison Type

Displays the geolocation level comparison (city, state, or country). If the geolocation level comparison does not fulfill the criteria, then an application level comparison is performed.

Device Hostname

Displays the name of the Gateway device.

Uplink Name

Displays the unique uplink name of the Gateway device.

Uplink Type

Displays the uplink type. For example, Broadband, MPLS, or LTE.

ISP

Displays the name of the WAN link service provider.

Root Cause

Displays the root cause, whether the impact is due to slow WAN link or slow response from the application server.