Application SLE (Marvis Minis)

Classifiers

The Application SLE classifiers help distinguish whether an application is reachable or whether the application performance is degraded due to network latency.

The Application SLE classifiers help differentiate between two critical conditions affecting applications—reachability and performance degradation caused by network latency.

• Application Reachability—This classifier indicates unsuccessful HTTP requests based on the validation data. Marvis Minis verifies application reachability by using default Internet connectivity URLs. You can also define custom URLs/FQDNs in the organization or site settings. See Add Custom URLs for Marvis Minis Validation .

  Marvis Minis considers an application as reachable if the response status code is either 200 (OK) or 408 (for default apps).

• Network Latency—This classifier lists the number of attempts when the application response is slow due to latency. The latency can be caused due to a network issue or an issue with the application. The latency is computed based on curl tests and comparison with a rolling baseline over the past 14 days. .

• Internet Services—This classifier lists failures experienced by users when accessing application due to:

  • Latency—Application slowness due to DNS latency. A high DNS latency can result in slower application page load times as the browser must wait longer to receive the IP address before it can start loading the page.

  • DNS—Application failures due to DNS resolution issues.

Root Cause Analysis for the Application SLE

You can use the information across the following tabs that display when you click ˅ beside Application.

• Timeline—See exactly when the issues occurred.

  Here is an example of how Marvis displays the timeline for the Application SLE. You can view the total number of attempts and the number of failed attempts for a specific date and time by hovering your mouse over the graph. In this example you can see that a total of 148 attempts were made to connect to the network on September 9 of which 2 attempts failed due to network latency and 2 attempts failed due to issues with the Internet services.

  

• Statistics—See the success rate, number of sites experiencing failures and the latency information. The Distribution graph indicates the latency. In this example, you can see that ~1000 connection attempts experienced a latency of up to 200 ms.

  

• Distribution—See which switches, APs, and VLANs were affected.

  

• Affected Items—See which applications were affected and how much each one contributed to the overall impact. Also see the individual failure rate for each application.

  

You can view in-depth information for applications at an organization or site-level. Here are the different options to view data:

• All applications in an organization

  This view is the default view as shown in the above example.

• A specific application at an organization level

  Click the specific application listed in the Affected Items tab (which is the default view shown above). You can view the details as shown in the following example.

  

• All applications in a site

  Select a site from the drop-down list on the top of the page, and navigate to the Affected Items tab. You can see the data for all the applications that experienced issues within the selected site.

  

• A specific application at a site level

  Select a site from the drop-down list on the top of the page and navigate to the Affected Items tab. Click an application to view the details. The site-level application view offers additional insights for the selected application, providing a more granular understanding of its performance and issues:

  • Network Latency

  • Packet Loss

  • Curl Latency

  • Traceroute

  Note:

  The Latency, Jitter, and Traceroute statistics are currently available as part of the Beta program for the enhanced Marvis Minis. Contact your account team to participate in the Beta program. Also, note that these sections are displayed only for an application at the site level.