Network Explorer / Tree
| Grey indicates a location with no activated devices. Note: there may be devices in Pending awaiting activation. | ||
| [n]The number of devices if greater than 1 in or below this folder, for details see Reporting Inventory. | ||
| Grey indicates a folder with no activated devices. Note: there may be devices in Pending awaiting activation. |
| Grey indicates a location with no activated devices. Note: there may be devices in Pending awaiting activation. |
| Collapse the tree | ||
| Expand the tree (only visible if the tree is collapsed) | ||
| Find locations or folders, and devices by name or IP address | ||
| Refresh the tree (only appears on hover) which updates it for folders or locations that have been added, changed or removed | ||
| Close all open folders | ||
| Click to see new features in place of the usual tree of folders and locations. A red background dot indicates new information is available. Once viewed, the red dot disappears until the next update. | ||
| | Opens an on screen simple message for passing information to the system provider | |
| | Use the star icon in the title bar to add folders or locations to your favourites. This pins them to the top of the Network Explorer tree. Find out more about Favourites. |
Alerting table
Reporting Insights
Reporting
If the new user does not log in, a further welcome email is sent after one week
If the new user still does not log in, a third further welcome email is sent after two weeks
Users can request their own password reset, if needed, as shown
| Icon | Text | Meaning | Action on Click |
|---|---|---|---|
| Add to favourites | Selected item is not currently a favourite | Adds item to favourites and refreshes the tree | |
| Remove from favourites | Selected item is already a favourite | Removes item to favourites and refreshes the tree | |
| Within favourite folder | Selected item has a parent folder already in favourites so it cannot be added or removed | No action |
Network Explorer / Tree
Collapse and expand the tree
Resize the tree by dragging the vertical blue line
Use this dialog to search for folders, locations, watches and controllers
| Column | Contents |
|---|---|
| Location | This is the Highlight location containing the device with the matching IP address. This is a link so clicking it moves the tree to that location. Note: There may be more than one location for an IP address. Results are sorted alphabetically by location name. |
| Device Name | If available, the name associated with a device. |
| Device IP (address) | This is the device IP address. |
| Interface (name) | This is the long interface name (IFDescr). |
| Interface IP (address) | This is the interface IP address. |
| Alias | If available, the alias associated with the interface (IFAlias). |
Busy Links is a count of bearers with peak load above 80%
Details page chart for Controller Status watch
Type specific stability alert on Controllers
Example initial new user email
Chart showing Availability and Health for IoT
Use the Theme dropdown to change UI mode
Reporting Inventory includes stack member details
Adjusted availability percent increases following the exclusions
Tunnels report with new Availability columns
Adjusted availability percent increases following the exclusions
Cisco Meraki Controller - Switches tab
Previous test chart
New test chart
Watch status card: Uplink with red Performance badge
Details page: Uplink connectivity test chart showing source and target plus metrics in the tooltip
Filter button - closed
Filter button - open
Filter reset
Service Tile options panel
Location options panel when Tiles selected
Stacked tile (Group by folder)
| A count of heat tiles in each state (red/amber/green) is displayed in the panel header at all times and adapts to the Any/All and Group by folder settings. | ||
| Use the radio button on each colour to hide or show those tiles in the display. | ||
| The "Filter reset" button returns colour settings to their default. The display resets to show all colours each time you log in. |
This setting is remembered when you next log in
The count of heat tiles in each state (red/amber/green) adapts to the Any/All setting
There is one watch in the Cellular Test location with a stability issue which has been ongoing for 1 hour.
| With "react to ANY issues" set, the Cellular Test location tile is red. | ||
| With "react to ALL issues" set, the Cellular Test location tile is amber. | The tile will only turn red if all 4 watches at the location are amber or red. |
Location tiles - react to ANY issues
Location tiles - react to ALL issues
| Condition | Precision Delay | MOS |
|---|---|---|
| Average response from the burst exceeds response target | Yes | Yes |
| Percentage of lost packets exceeds packet loss target | Yes | Yes |
| Jitter measured over the burst exceeds jitter target | Yes | Yes |
| MOS Score is less than target | N/A | Yes |
Filter button - closed
Filter button - open
Filter reset
| Affects | Information | Details |
|---|---|---|
| AP Traffic In/Out | Total volume of Wireless traffic flowing in and out of the Access Point (AP) | |
| AP Utilisation | The percentage utilisation of the two radio channels, 2.4GHz and 5GHz, on that AP | |
| AP Status | Whether a AP is up or down. This considers (a) connectivity to the AP is up and running, and (b) each radio on the AP is up and working. If any of these report down from an operational perspective, Highlight reports a problem with the AP. 'Administrative' down status (where the AP or an interface has been deliberately shut down by the administrator) will not show as an outage or trigger an alert. Highlight also detects reboots of the AP and shows them as events / blips. | |
| Client Count | The number of client devices connected to the AP | |
| Congestion | Highlight derives a metric to indicate congestion level on the AP radio networks. For consistency with other types of link, the metric used is the percentage of send attempts that require retransmissions. Since a certain level of retries is entirely normal, Highlight looks for retry levels above a certain threshold which Admin users can configure to avoid spurious alerts. Congestion is not calculated unless traffic volumes are more than 1 frame per second. | |
| Signal Problems | Highlight gives an indicative picture of how well clients are connecting by monitoring the percentage of connected client devices which are reporting poor signal strength (poor signal means SNR (Signal-to-Noise Ratio) of 1 or 2 bars (under 20 decibels). | |
| AP CPU Load | The CPU Utilisation / Load on that AP, as a percentage |
Percent of Site Load columns on the far right
A Controller Status watch alerts if the parent controller is down
| Field name | Description | Code | In email? | In trap? | In webhook? |
|---|---|---|---|---|---|
| Subject | The subject of the email: location - alert description - report | {{Subject}} | Yes | Yes - as "alertSummary" | |
| Alert action IDs | The unique ID(s) for the alert action(s) which generated the alert, found on Status > Alerting and Reporting > Audit log | {{AlertIds}} | Yes | Yes | |
| Alert Names | The name(s) for the alert action(s) which generated the alert, found on Status > Alerting | {{AlertNames}} | Yes | Yes | |
| Alert Link | A shortcut to the alert action in Status > Alerting | {{AlertLinkUrl}} | Yes | Yes | |
| Time - Highlight formatted | The UTC time the alert occurred formatted "HH:mm on Month Day Year" | {{TimeStampStringUtc}} | Yes | ||
| Time - machine formatted | The UTC time the alert occurred, uses local date format | {{TimeStampUtc}} | Yes | Yes (UTC and local) | Yes |
| Time - in the UK | The UK time the alert occurred, available in three codes | {{TimeStampUk}} {{TimeStampStringUk}} {{TimeStampStringUkWithOffset}} | Yes | ||
| Folder | The path to the parent folder of the location with the alert | {{Folder}} | Yes | Yes | Yes |
| Location | The name of the location where the watch exists | {{LocationName}} | Yes | Yes | Yes |
| Location Alert Time - Highlight formatted | The time the alert occurred in the watch location time formatted "HH:mm ''on'' MMMM dd yyyy (''UTC''zzzz)" | {{TimeStampStringLocation}} | Yes | ||
| Location Alert Time - machine formatted | The time the alert occurred in the watch location time, uses local date format | {{TimeStampAtWatchLocation}} | Yes | Yes | |
| Report | The name of the watch If watch has a description, that is shown followed by watch name in brackets *See notes on classes, VLANs and performance tests | {{Report}} | Yes | Yes | |
| Problem | What was affected (Stability/Load/Health), see previous section - Problem text in alerts - Amber/Red alert raised/cleared | {{Problem}} | Yes | Yes | Yes |
| Problem | Additional fields which provide details on the problem are listed below | ||||
| Problem: Stability issue code | The issue code associated with Stability transitions (see next section - Stability issue codes) | {{StabilityIssueCode}} | Yes | Yes | |
| Problem: Stability Issue Description | Webhook only | {{StabilityIssueDescription}} | Yes | ||
| Problem: Has Stability Issue | Webhook only - True/False | {{HasStabilityIssue}} | Yes | ||
| Problem: Level 3 metric | Stability, Load or Health | {{Level3Metric}} | Yes | Yes | Yes |
| Problem: Level 2 metric | See previous section - Problem text in alerts | {{Level2Metric}} | Yes | Yes | Yes |
| Problem: Colour | Red, Amber or Green | {{Colour}} | Yes | Yes | |
| Problem: Direction | Up or down | {{Direction}} | Yes | Yes | |
| Problem: Metric Value | Current value of the level 2 metric, as a percentage of the threshold | {{MetricValue}} | Yes | Yes | Yes |
| Problem: Fuel Gauge Value | Current value of the fuel-gauge which triggered the event | {{FuelGaugeValue}} | Yes | Yes | Yes |
| Problem: Metric Description | See previous section - Problem text in alerts | {{MetricDescription}} | Yes | Yes | Yes |
| Name | Name of the watch that caused the alert, a unique identifier | {{Name}} | Yes | Yes | Yes - as "watchName" |
| Watch type | Type of watch that caused the alert e.g. bearer, ICMP test etc. | {{WatchTypeName}} | Yes | Yes | |
| Device address | IP address for the device of the watch that caused the alert | {{DeviceAddress}} | Yes | Yes | Yes |
| Reference | Note this can be set individually for bearers and their subwatches (classes and VLANs) which may assist parsing of alerts | {{Reference}} | Yes | Yes - as "referenceText" | |
| Watch ID | Internal reference number (Trap only) | N/A | Yes | ||
| URL | Is URL available? Use code before and after | {{#LinkUrl}} {{/LinkUrl}} | Yes | Yes | |
| URL | A shortcut to the Details page of the affected watch | {{LinkUrl}} | Yes | Yes |
| VLANs | If the watch is a VLAN then Report is set to VLAN "Vlan interface” |
| Class | If the watch is a traffic class then Report is set to Traffic Class "Class Tag” (as found in the Edit Watch dialog) |
| Performance test | If the watch is a performance test then Report is set to “test type from source address to target address (IP or URL).” If descriptions are available for the source, target or both, descriptions overwrite addresses. |
| Field name | Description | Code | In email? | In webhook? |
|---|---|---|---|---|
| Broadband watch | Is this a broadband watch? Use code before and after | {{#IsBroadbandSpeedAlert}} {{/IsBroadbandSpeedAlert}} | Yes | Yes |
| Broadband downstream speed Kb | {{BroadbandSampleSpeedKbps}} | Yes | Yes - as "broadbandDownstream SpeedKbps" | |
| Broadband threshold speed Kb | {{BroadbandSpeedThresholdKbps}} | Yes | Yes - as "broadbandAlert ThresholdKbps" | |
| Cellular watch | Is this a cellular watch? Use code before and after | {{#IsCellular}} {{/IsCellular}} | Yes | Yes |
| Cellular signal strength (Score) | {{CellularSignalStrength}} | Yes | Yes | |
| Cellular signal strength threshold (Score) | {{CellularSignalThreshold}} | Yes | Yes | |
| Critical port watch | Is this a critical port on a switch? Use code before and after | {{#HasCriticalPortInfo}} {{/HasCriticalPortInfo}} | Yes | Yes |
| Critical port | {{CriticalPort}} | Yes | Yes | |
| Critical slot | {{CriticalSlot}} | Yes | Yes | |
| Port interface name | {{PortInterfaceName}} | Yes | Yes | |
| Port interface alias | {{PortInterfaceAlias}} | Yes | Yes | |
| Performance test watch | Is this a performance test? Use code before and after | {{#IsPerfTest}} {{/IsPerfTest}} | Yes | Yes |
| Test Name (API Name) | {{ApiName}} | Yes | Yes | |
| URL Link to External system | {{ExternalLinkUrl}} | Yes | Yes | |
| Site link | Is watch a site link? Use code before and after | {{#IsSiteLink}} {{/IsSiteLink}} | Yes | Yes |
| Total linked sites at location | {{TotalLinkedSites}} | Yes | Yes | |
| Active linked sites (based on stability) at location (aka Site links Up) | {{SiteLinksUp}} {{ActiveLinkedSites}} | Yes | Yes | |
| Down linked sites at location - true/false | {{DownLinkedSites}} | Yes | Yes | |
| Tunnel (SD-WAN) | Is watch a tunnel? Use code before and after | {{#IsTunnel}} {{/IsTunnel}} | Yes | Yes |
| Tunnel load threshold (82% fixed) | {{TunnelTrafficLoadThresholdPercent}} | Yes | Yes | |
| Tunnel traffic load | {{TunnelTrafficLoadPercent}} | Yes | Yes | |
| Wireless Access Point | Is watch a WAP? Use code before and after | {{#IsWirelessAccessPoint}} {{/IsWirelessAccessPoint}} | Yes | Yes |
| AP Serial number | {{WapSerialNumber}} | Yes | Yes | |
| AP Location | {{WapLocation}} | Yes | Yes |
| Issue code | Issue description |
|---|---|
| #CNA | Issue Code Not Available |
| #OIU | Ongoing issue cause unknown or monitoring an unknown interface |
| #TBO | Transients or brief outages |
| #DRP | Device restarted powered off/on |
| #RAD | Circuit reported as Down |
| #OOS | Circuit taken out of service |
| #UOT | Unknown event type |
Alert dialog
Alert on type
Alert suppressed at subfolders
| Information | Format | Details |
|---|---|---|
| Watch ID | Number | Highlight’s ID number for the Watch which generated the alert |
| Watch Name | String | The short name (reference, mnemonic etc.) for the Watch |
| Folder Name | String | The name of the folder containing the Watch |
| Location Name | String | The name of the location containing the Watch |
| Level 3 metric | Number | Stability, Load or Health |
| Level 2 metric | Number | A reference for the element causing the alert, e.g. LinkStability |
| Metric value | Number | Current value of the level 2 metric, as a percentage |
| Fuel-gauge value | Number | Current value of the fuel-gauge which triggered the event |
| Description | String | Text description of the broken metric |
| Timestamp UTC | String | The UTC time at which the alert was raised |
| Timestamp local | String | The local time at which the alert was raised |
| Reporting Device | IP Address | The IP Address the trap came from |
| Switch critical port slot** | Number | The slot of the port if a critical port switch event |
| Switch critical port** | Number | The port if a critical port switch event |
| Method | Webhook |
| Send to | Enter a URL generated by the webhook receiver (required field) |
| Test button | Is available for webhook alerts only and sends a sample webhook (see next section) to the URL |
| Connected | Testing confirms the URL is valid |
| Cannot connect | Shown if the URL is not valid, for possible reasons refer to Troubleshooting webhook alerts |
| Notify on failure | Shows your email address by default but can be changed. Separate multiple addresses with commas.
This field is optional. Delete the email address if you do not wish to receive an email. |
| Save button | On save, a unique ID number is created for each alert allowing you to track who made changes to an alert. The ID is visible in the alerting table, when editing an alert and in Reporting Audit Log as the item name. When saving a webhook alert, a test of the Send to URL is performed. This test must be successful to save the alert. |
| Field ID | Example contents | Notes |
|---|---|---|
| activeLinkedSites | 2 | integer |
| alertIds | 297402 | integer |
| alertLinkUrl | https://kfv-services.highlighter.net/portal/index.html#/status/alerting/19739/%7b%22editItemId%22%3a57661%7d | string URL link to the alert in Highlight, users can follow for direct access |
| alertNames | Cellular Alert | may be empty, otherwise string |
| alertSummary | KFV Services - Red Alert Raised - LinkHealthADSL (HO-Secondary) | combined string showing Location - Colour Raised/Cleared - Watch Name |
| broadbandDownstreamSpeedKbps | 5272 | always empty if IsBroadbandSpeedAlert is false, otherwise integer |
| broadbandAlertThresholdKbps | 2048 | always empty if IsBroadbandSpeedAlert is false, otherwise integer |
| cellularSignalStrength | 3.2 | always empty if IsCellular is false, otherwise decimal |
| cellularSignalThreshold | 3.5 | always empty if IsCellular is false, otherwise decimal |
| colour | Red | red, amber or green |
| criticalPort | 2 | integer, this field only appears if a value has been set |
| criticalSlot | 2 | integer, this field only appears if a value has been set |
| deviceAddress | 10.0.0.1 | IP address |
| direction | up | up (active) or down (inactive) |
| downLinkedSites | false | boolean: true if watch is a site link and down |
| folder | KFV Services » DataCentre | path with “»” as separator |
| fuelGaugeValue | 110 | interger |
| hasCriticalPortInfo | true | boolean: true or false |
| hasStabilityIssue | true | boolean: true or false |
| isBroadbandSpeedAlert | false | boolean: true or false |
| isSiteLink | true | boolean: true or false |
| isTunnel | true | boolean: true or false |
| isWirelessAccessPoint | false | boolean: true or false |
| level3Metric | Stability | stability, load or health |
| level2Metric | Link Stability | see Problem text in alerts for examples |
| linkUrl | https: //kfv-services.highlighter.net/portal/index.html#/details/landing/19739/23298/%257B%2522today%2522%253Atrue%257D | string URL link to watch in Highlight, users can follow for direct access |
| locationName | Head Office | string |
| metricDescription | Link Stability | string |
| metricValue | 120 | integer |
| portInterfaceAlias | Link to SG500-28 | string |
| portInterfaceNamw | GigabitEthernet1/0/44 | string |
| problem | Link-Availability - Red alert raised | string |
| referenceText | 1067504-1718672 | string |
| siteLinksUp | 1 | the number of site links in the same location still up, set to null if the watch is not a site link |
| stabilityIssueCode | #DRP | can be empty, see full list of stability issue codes |
| stabilityIssueDescription | Device restarted powered off/on | can be empty, see full list of stability issue descriptions |
| text | KFV Services - Red Alert Raised - LinkHealthADSL (HO-Secondary) | combined string showing Location - Colour Raised/Cleared - Watch Name (same as alertSummary) |
| timeStampAtWatchLocation | 2020-02-14T12: 23: 26.4304015+02: 00 | (Date) YYYY-MM-DD T (Time) HH:MM:SS.sssssss + offset from UTC in HH:MM |
| timeStampUtc | 2020-02-14T10: 23: 26.4304015+00: 00 | (Date) YYYY-MM-DD T (Time) HH:MM:SS.sssssss Z |
| totaLinkedSites | 1 | integer |
| tunnelTrafficLoadPercent | 90 | integer - percentage |
| tunnelTrafficLoadThresholdPercent | 82 | integer - percentage - fixed value |
| wapLocation | WapLocation | string, always empty if IsWirelessAccessPoint is false |
| wapSerialNumber | WapSerialNumber | string, always empty if IsWirelessAccessPoint is false |
| watchName | HO-Secondary | string |
| watchTypeName | WatchTypeName | string |
| Column | Explanation |
|---|---|
| Logo | added from a library of logos; if no logo is available, a generic category logo will be shown instead. Contact us for any logo issues |
| Name | as discovered |
| Locations | for the folder selected in the Network Explorer tree, the total number of locations where this application is found. Note: this column is not shown when a location is selected in the tree |
| Category | the application category logo, a full list of application categories with sample applications is available; hover to see the category name |
| First/Last Seen | a date based on UTC time. The date is amber if it's been less than 36 hours since it first appeared (for First Seen) or more than 90 days since it last appeared (for Last Seen). |
| DSCP | the DSCP name and value (in brackets), this may show: Undefined: if the value does not map to a DSCP name None: if the DSCP value is not set |
| Class | the traffic class of an application, for example Best effort or Priority, which may show: Multi - N: if the application runs over more than one class, N is the number of classes detected Undefined: if the DSCP value is unmapped in Highlight to a class name The classes are those defined in the folder class definitions. |
| Group | shows which group(s) an application belongs to, see Groups section below |
| Usage | in bytes, being the reported volume for the period selected. A longer purple bar indicates higher usage |
Details Header
Details menu
| Day | A single 24 hour period (may be 23 or 25 hours on daylight savings adjustment dates) |
| Week | A Highlight week is Sunday to Saturday |
| Month | A calendar month beginning on the first |
| No colour / grey / green | No issue or for week, month or any day other than today |
| Amber | At least one issue, this watch is alerting, meaning a threshold has been breached |
| Red | At least one issue and ths watch has been alerting for some time |
This Traffic Load section is amber. The Outbound load has been exceeding the 80% threshold for more than 30 minutes.
This Line Availability section is red. There has been an ongoing issue for more than 6 hours.
| Colour | Percentages | Meaning |
|---|---|---|
| Black Red | 300% | Percentages are capped at 300% |
| Maroon | 200% | |
| Red | 101% | Greater than the bandwidth of the line |
| Pink | 100% | The configured or discovered bandwidth of the line |
| Orange | 80% | By default, Highlight alerts at 80% |
| Amber | 60% | |
| Green Amber | 20% | |
| Green | 0% |
| Day | Shows multiple data points per hour (one for each polling period, usually one to five minutes) |
| Week | Shows 24 data points per day (every hour), in MinMax view, Average for each hour is shown along with MinMax values |
| Month | Shows 6 data points per day (every 4 hours), in MinMax view, Average for each 4 hour period is shown along with MinMax values |
Summary with percent selected
| Colour | Ignored | Green | Green Amber | Amber | Orange | Red |
|---|---|---|---|---|---|---|
| Errors/Discards | Up to 0.10% | 0.11 to 0.50% | 0.51 to 1.00% | 1.01 to 2.50% | 2.51 to 5.00% | Greater than 5.00% |
| Colour | Grey line | Green line | Green | Amber | Orange | Red |
|---|---|---|---|---|---|---|
| CPU util | 0% | Up to 50% | 51% to 65% | 66% to 80% | 81% to 95% | 96% to 100% |
| Column | Description |
|---|---|
| Time | the date and time of each sample (matching the time zone selected on the Details page) |
| In | the total bytes received since the previous sample |
| Out | the total bytes sent since the previous sample |
| Util In | the average speed of traffic calculated from the received bytes value during this time period, expressed as a percentage of the configured/discovered bandwidth In (see example below) |
| Util Out | the average speed of traffic calculated from the sent bytes value during this time period, expressed as a percentage of the configured/discovered bandwidth Out (see example below) |
| Error | the number of errors reported in this time period expressed as a percentage of the number of packets received |
| Discards | the number of discarded packets reported in this time period expressed as a percentage of the number of packets sent |
| true | Impacting |
| true | Exclusions |
| true | Non-impacting |
| Day | Shows all events for the day |
| Week | Shows each hour with events on different lines within the same hour shown |
| Month | Shows each 4 hour period with events on different lines within the same 4 hours shown |
| Number | Blip colour | Issue | Effect in Highlight | Included in Total outages? |
|---|---|---|---|---|
| 1 | Amber | Transient or brief outages | Decrements stability | Yes |
| 2 | Red | Circuit reported as down, or period of non-contact ends in a device restart | Stability previously decremented (only red after contact re-established) | Yes |
| 3 | Maroon | Circuit taken out of service | Decrements stability | Yes |
| 4 | Turquoise | Device configuration changed | No effect | No |
| 5 | Black | Device restarted, powered off/on | No effect | No |
| 6 | Mint | Unknown event type | No effect | No |
| 7 | Blue | No data, device not contactable or monitored interface does not exist | Stability previously decremented (only blue after contact re-established) | Custom |
| 8 | Mustard | Ongoing issue, cause unknown or monitoring an unknown interface | Decrements stability and turns watch amber/red | Custom |
| Option | Description |
|---|---|
| Downstream - today | Displayed as green if above the threshold and red if below for 'Today' view only |
| Downstream - not today | Displayed as blue for all historical views other than today |
| Upstream | Displayed as darker blue for all views |
| Relearn button | Use this if the current threshold is inaccurate due to changes on the line. Relearning the threshold can take a period of days, depending on the settings in the Alerting Thresholds dialog |
| Reset zoom button | If you click, hold and drag across the chart to zoom in then this button appears in the top right of the chart - click to revert to the full time period. See separate section on Zoom options below. |
| Day | Shows multiple data points per hour (the lowest speed seen for each polling period, usually three minutes) |
| Week | Shows 24 data points per day (every hour) |
| Month | Shows 6 data points per day (every 4 hours) |
| Day | Shows multiple data points per hour (one for each polling period, usually five minutes) |
| Week | Shows 24 data points per day (every hour), Average for each hour is shown along with Min/Max values if selected |
| Month | Shows 6 data points per day (every 4 hours), Average for each period is shown along with Min/Max values if selected |
| Day | This depends on the test frequency set on the external system |
| Week | Shows 24 data points per day (every hour), Average for each hour is shown along with Min/Max values |
| Month | Shows 6 data points per day (every 4 hours), Average for each period is shown along with Min/Max values |
Perforamance chart - UDP Echo
| Day | Shows up to 6 data points per polling period (usually three minutes) |
| Week | Shows 24 data points per day (every hour), Average for each hour is shown along with Min/Max values |
| Month | Shows 6 data points per day (every 4 hours), Average for each period is shown along with Min/Max values |
| Colour | Green line | Amber | Orange | Pink | Red | Maroon |
|---|---|---|---|---|---|---|
| Packet Loss % | 0% | 0.01% to 20% | 20.01% to 40% | 40.01% to 60% | 60.01% to 80% | 80.01% to 100% |
| Day | Shows a data point per polling period (usually three minutes), Average for each test is shown along with Min/Max values |
| Week | Shows 24 data points per day (every hour), Average for each hour is shown along with Min/Max values |
| Month | Shows 6 data points per day (every 4 hours), Average for each period is shown along with Min/Max values |
| Colour | Green line | Amber | Orange | Pale red | Maroon |
|---|---|---|---|---|---|
| Jitter % | 0% to 50% | 50.01% to 65% | 65.01% to 80% | 80.01% to 100% | Above 100% |
| Score | Meaning |
|---|---|
| 5 | Perfect |
| 4 | Good |
| 3 | Fair |
| 2 | Poor |
| 1 | Unusable |
In the example GIF, the IP Address is changed to display as salesforce
| Day | Shows multiple data points per hour (one for each polling period, usually one to five minutes) |
| Week | Shows 24 data points per day (every hour), Maximum for each hour is shown |
| Month | Shows 6 data points per day (every 4 hours), Maximum for each 4 hour period is shown |
| Colour | Grey line | Green line | Green | Amber | Orange | Red |
|---|---|---|---|---|---|---|
| CPU util | 0% | Up to 50% | 51% to 65% | 66% to 80% | 81% to 95% | 96% to 100% |
| Priority | Blip Colour | Issue |
|---|---|---|
| 1 | Red | AP reported as Down |
| 2 | Maroon | AP taken out of service. If the access point has been shut down deliberately on the controller. |
| 3 | Blue | No data, controller is not contactable |
| 4 | Turquoise | The radio frequency has changed channel between polls |
| 5 | Green | AP is up |
| Day | Shows multiple data points per hour (one for each polling period, usually one to five minutes) |
| Week | Shows 24 data points per day (every hour), Maximum for each hour is shown |
| Month | Shows 6 data points per day (every 4 hours), Maximum for each 4 hour period is shown |
| Green | Values are at or below the threshold |
| Red blips | Values exceed the threshold |
| Grey | No samples or client count of 0% |
| Day | Shows multiple data points per hour (one for each polling period, usually one to five minutes) |
| Week | Shows 24 data points per day (every hour), Maximum for each hour is shown |
| Month | Shows 6 data points per day (every 4 hours), Maximum for each 4 hour period is shown |
| Green | Values are at or below the threshold |
| Red blips | Values exceed the threshold |
| Grey | No samples or congestion of 0% |
| Feature | Aruba AirWave | Aruba Instant On | Cisco | Cisco Meraki | Extreme | Ruckus | Ubiquiti |
|---|---|---|---|---|---|---|---|
| Volume | false | true | true | true | true | true | true |
| CPU utilisation | false | true | false | false | false | false | true |
| Availability - Red blips | true | true | true | true | true | true | true |
| Availability - Maroon blips | true | true | true | false | false | false | true |
| Availability - Blue blips | true | true | true | true | true | true | true |
| Availability - Turquoise blips | true | true | true | false | false | true | true |
| Client Count | true | true | true | true | true | true | true |
| Signal Problems | true | true | true | false | true | true | true |
| Channel Load | false | true | true | true | true | true | true |
| *Channel Load 6 GHz | false | false | false | true | true | false | false |
| Congestion | false | true | true | false | false | false | false |
| Feature | Aruba AirWave | Aruba Instant On | Cisco | Cisco Meraki | Extreme | Ruckus | Ubiquiti |
|---|---|---|---|---|---|---|---|
| WAP Location | false | true | true | false | false | false | false |
| WAP Name | true | true | true | true | true | true | true |
| Serial number | true | true | true | true | true | true | true |
| WAP type | true | true | true | true | true | true | true |
| SSID | false | true | true | false | true | false | false |
| WAP Util Avg/95pc/Peak | false | true | true | false | false | true | true |
| WAP Volume | false | true | true | true | true | true | true |
| Congestion | false | true | true | false | false | false | false |
| Client Avg/Peak | true | true | true | true | true | true | true |
| Signal Problems | false | true | true | false | true | true | true |
| Day | Shows multiple data points per hour (one for each polling period, usually one to five minutes) |
| Week | Shows 24 data points per day (every hour), in MinMax view, Average for each hour is shown along with MinMax values |
| Month | Shows 6 data points per day (every 4 hours), in MinMax view, Average for each 4 hour period is shown along with MinMax values |
| Blip Colour | Issue | Effect in Highlight | Included in Total outages? |
|---|---|---|---|
| Red | Tunnel down | Stability previously decremented (only red after contact re-established) | Yes |
| Blue | API call failure - recovered (patched from Mustard to Blue) | Stability previously decremented (only blue after contact re-established) | Custom |
| Mustard | API call failure - ongoing | Decrements stability and turns watch amber/red | Custom |
| Day | Shows multiple data points per hour (one for each polling period, usually one to five minutes) |
| Week | Shows 24 data points per day (every hour), Maximum for each hour is shown |
| Month | Shows 6 data points per day (every 4 hours), Maximum for each 4 hour period is shown |
| Priority | Colour | Issue |
|---|---|---|
| 1 | Red blip | Parent controller reported as down or is not contactable |
| 2 | Green line | Parent controller is up |
| 3 | Grey line | No data |
| Day | Shows multiple data points per hour (one for each polling period, usually one to five minutes) |
| Week | Shows 24 data points per day (every hour), Maximum for each hour is shown |
| Month | Shows 6 data points per day (every 4 hours), Maximum for each 4 hour period is shown |
| Priority | Blip Colour | Issue |
|---|---|---|
| 1 | Red | Agent reported as Down |
| 2 | Maroon | Agent taken out of service. If the Agent has been shut down deliberately on the controller. |
| 3 | Blue | No data, controller is not contactable |
| 4 | Green | Agent is up |
Switch port filters: All, Active and Crticial GIF
| Colour | Grey line | Green line | Green | Amber | Orange | Red |
|---|---|---|---|---|---|---|
| Load | No data | 0% to 50% | 51% to 65% | 66% to 80% | 81% to 95% | 96% to 100% |
| Colour | Grey line | Green line | Green | Amber Green | Amber | Orange | Red | Maroon |
|---|---|---|---|---|---|---|---|---|
| Health | No data | 0 | 1 | 2 - 11 | 12 - 23 | 24 - 52 | 53 - 74 | 75 - 100 |
Sensitivity settings for the example below
| Metric | Example condition for bad sample | Samples to turn from green to amber | Samples to red |
|---|---|---|---|
| Stability | Port is down | 2 | 2 more; 4 in total |
| Load | >60% | 5 | 5 more; 10 in total |
| Health | Errors per 1000 frames rate >1; | 10 | 10 more; 20 in total |
| Metric | Example condition for good sample | Samples to turn from red to amber | Samples to green |
|---|---|---|---|
| Stability | Port is up | 3 | 3 more; 6 in total |
| Load | ≤60% | 6 | 6 more; 12 in total |
| Health | Errors per 1000 frames rate ≤1 | 12 | 12 more; 24 in total |
| Day | Shows multiple data points per hour (one for each polling period, usually one to five minutes) |
| Week | Shows 24 data points per day (every hour), Maximum for each hour is shown |
| Month | Shows 6 data points per day (every 4 hours), Maximum for each 4 hour period is shown |
| Colour | Issue |
|---|---|
| Red blip | Switch Slot reported as Down |
| Blue blip | No data, controller is not contactable |
| Green line | Switch Slot is up |
| Grey line | No data |
| Day | Shows multiple data points per hour (one for each polling period, usually one to five minutes) |
| Week | Shows 24 data points per day (every hour), Maximum for each hour is shown |
| Month | Shows 6 data points per day (every 4 hours), Maximum for each 4 hour period is shown |
| Priority | Colour | Issue |
|---|---|---|
| 1 | Red blip | Camera, sensor or generic device reported as Down |
| 2 | Blue blip | No data, controller is not contactable (Blue is not an option for generic devices) |
| 3 | Green line | Camera, sensor or generic device is up |
| 4 | Grey line | No data |
| Colour | Webex state |
|---|---|
| Green line |
|
| Red blip | Down is the safe default for unrecognised values.
|
| Blue blip | Unreachable:
|
| Colour | Meaning |
|---|---|
| Red blip | Issue: Alerting |
| Green line | OK - no issue |
| Grey line | No data |