Meraki Assurance Overview Page
What is Assurance Overview?
Assurance Overview is a new assurance feature/page we are building to enable network administrators to understand the overall health of their network across their entire stack and to provide quality experiences to their customers. The goal is to empower network administrators to easily monitor their network health across the full stack and quickly identify and troubleshoot problematic areas.
Scope
The initial scope of the Assurance Overview page will cover the core infrastructure products. MX, MS, MR
What it is
-
Enable network administrators to understand the overall health of their network across their entire stack.
-
Empowers network administrators to quickly monitor network health and easily identify and troubleshoot problematic areas.
Goal of the Assurance Overview
-
Create a unified assurance experience.
-
Improve network administrator's experience so they can accurately evaluate and maintain quality of experiences for end-users.
-
Improve end-user’s experience so they can securely, seamlessly, and reliably access business critical network resources.
How do I provide feedback?
Providing feedback is as easy as selecting the “Give Feedback” blue tab on the right side of screen (make sure ad blockers are off for this page) and the “Give your feedback” button in the lower right corner of the screen (See figure below).
Where do I find the Assurance Overview?
When you log into the Dashboard you will be greeted with a new menu item in the left hand navigation list. The Assurance Overview page (along with other assurance related tools) can be found here. This will bring you to the new Assurance Overview page, here you will see multiple modules that report various aspects of network health as it relates to the overall network, clients, devices, and applications.
What is on the Assurance Overview Page?
-
The top module shows the network health score, this is a combined score taking into account different weighted aspects of network health to give an overall health of the environment
-
The timeline next to it gives you a look at the network health over a time span governed by the time selector at the top
-
Next are the impact sections which give you a view as to how many clients are impacted for each type of alert that is/has been active in the system.
-
The Client module breaks this down by connection type, wireless, remote, and wired
-
The Network devices module shows context for the Cisco first party devices in the network
-
The applications module provides information on how large the client impact is for errors in the Application environment. This module is sourced from Thousand Eyes data that is entered elsewhere in the Dashboard for web services that you are tracking.
Client Impact Module
-
You can highlight and select one of the buckets in the modules and this will open a side drawer that slides in from the right of the screen, with more details about that specific bucket.
-
In this side drawer you’ll be given a list of specific metrics and a further breakdown of the client impact.
-
Clicking on one of the metrics will provide further details, drilling down to the actual client list level.
-
At the top you’ll also see a pie chart visualization that provides further visual breakdown to help assess priority.
-
Here you can see details on the clients or be taken to the client details page to get more information on that client.
-
On the details page there are search and filter boxes to help refine what you are looking for.
-
Clicking on one of the client links under impacted clients in the detail side drawer will take you to the client detail page
-
Here you get a full picture of what Dashboard and Assurance know about the client to aid in troubleshooting.
Network Devices Impact Module
-
Selecting one of the buckets in the Network Devices Module will open a side drawer (slide in from right) and give you context on the metrics impacting that device in the time period represented in the time filter
-
Selecting a specific metric will drill down into a list of the impacted devices for that metric.
-
Clicking on a device name in the impact list (like the client impact module) will take you to the device's detail page to get more information about the device and its current condition
Application Impact Module
The Application Impact Module provides simplified and rich visibility into the health and current status of the customer's critical applications. This module leverages our native integration with the ThousandEyes Enterprise agent, which runs natively inside the Meraki MX Appliance and provides active monitoring data.
An application will appear in this section after it has been configured to be monitored using the Active Application Monitoring workflow under the Insight Menu.
Requirements
-
Successful onboarding and installation of the ThousandEyes agent on the Meraki MX. For more details please refer to our Solution Requirements section in the Meraki MX ThousandEyes configuration guide.
-
SD-WAN+ Licensing.
The application module consists of two sections, the main Application view that’s available on the Assurance Overview page and the detailed information drawers, which appear on the right side of the Dashboard once they are invoked.
Main Application View
The Main Application view provides a quick overview of the performance and health of the applications being monitored in the network. This view contains several data points that reflect the impact of any outage or performance degradation affecting the applications during the time frame specified above.
As seen below, all the monitored applications are listed from worst (top) to best performing as dictated by their individual score.
Each application card shows a summary of the monitored application’s status. If an outage or issue is present, it will highlight the number of potentially impacted clients and the number of issues affecting them.
Score breakdown
Blue Score: This score is the ThousandEyes-based Application score. It’s shown here without modification besides the needed aggregation and averaging to ensure that it contains all the measurements from the selected time period. Metrics that are used to calculate this score are: Packet Loss, Latency, Jitter and Application Availability (any HTTP response code from the Application greater than 400 results in the App being unavailable).
Red Score: Also known as the Customer Experience Score or Impact Score, is a score calculated based on the ThousandEyes score plus a weight that accounts for the number of potentially impacted clients. The idea is to summarize the Applications’ health and performance across the network and the impact of the outage on their users. This aggregation is also done based on the selected time period.
Points change: Show how the score has changed when compared to the previous time period. For example, if the data requested is for the last 2 hours it will show how the score has changed from the previous period of 2 hours.
Detailed Information Drawers
Once an application card is clicked, the detailed information drawers are opened to the right side of the dashboard. Currently, they are three levels deep and provide information following the progressive disclosure principle. These drawers allow deep diving into the ThousandEyes test data as well as all the Alerts or Issues that exist for a given application. The first drawer can be brought up by clicking on a desired application. See an example below:
First Drawer: Network Layers
The goal of the first drawer is to highlight the potential network layers where the issue or outage might exist. Currently, they are divided into two:
- Internet Layer: It focuses on network issues that are present from the location where the ThousandEyes Enterprise agent is located up to the Application server, meaning anything across the Internet. The metrics that we capture are Packet Loss and Latency across the whole path.
- Application Layer: This layer showcases any issues with the application HTTP server itself, meaning any unexpected HTTP response or undesired response time. The metrics captured are Availability (Any HTTP response code > 400 is considered unavailable) and Response Time.
All the other metrics in the drawer are self-explanatory.
Second Drawer: Layer’s detail metrics
The second drawer provides detailed information on the value of the metrics that are captured for each layer and current or previous alerts that caused an outage or a performance degradation event. For example, for the Internet card, we see the Loss and Latency metrics and their values during the selected time period:
Most of the information on these pages is self-explanatory, but something to highlight is that on the line graphs, if the background is red, an alert was active during that time. We also provide a list of the start and end times for these alerts or issues at the bottom of the drawer. If an ongoing issue is detected, its end time will be shown as Active.
The second drawer will always include any information on triggered alerts that result in a performance issue for the network clients. If multiple alerts occur during that time and some are resolved, they will be ordered from latest to oldest, with the active alert always at the top. The third and final drawer can be accessed by clicking on one of the alerts.
Third Drawer: Client Impact and ThousandEyes Redirection
The third and final drawer focuses on showing the impacted clients by the previously selected alert. It can be accessed by clicking on one of the Alerts shown on the second drawer table.
This drawer provides information on which clients were potentially affected by the outage selected previously. It also allows redirection to the ThousandEyes Dashboard, where more information on the issue can be seen if desired. Please keep in mind that the ThousandEyes portal will require your login information if you have not already logged in.
Troubleshooting ThousandEyes data in the Assurance Overview Page
Troubleshooting the application section should be done using the same tools and methods used for general Dashboard troubleshooting, such as browser developer tools and HAR captures. If you need help please reach out to our Meraki Support team.