Smiley Face

  • Represents the aggregated summary of the client experience
  • Click on Smiley: Summary of ongoing/resolved alerts
  • Hover over Smiley/Sensor: Snapshot of past 24 hours experience listed
  • Below Smiley supports up to 7 levels of hierarchy
  • Sorted via error sites, then alphabetically

Traffic Lights
Mirror client onboarding and experience using network services & applications

  • Services: Networks onboarded, DORA process, Auth/Captive Portal timings
  • Internal: Tests important to the business or on the inside of network/firewall
  • External: Pinpoint is the ISP/User/Client having issues
  • Dropbox, YouTube tests use actual service to download results
  • Click on a test to view test results across sensor environments

Map View; Block View; and Hierarchy Groupings:

  • Left Icon: Global views, locations, grouping, status 
  • Middle Icon: Block View - Route directly to specific sensors
  • All Groups: Drill into locations utilizing Google Location

Search; Filters; Alerts; Settings; What’s New: 

  • Filter views
  • Account setup; documentation
  • What’s new when significant new features are available

Keyboard Shortcuts: 

n - notifications and the bell
m
– menu
f
– filters
w
- switch user
s
– settings
spacebar
– search
arrows left and right -
move between main dash/map view

Support - Via Intercom

From your main page - click on a Sensor to take you to the next detailed page: 

SENSOR DETAILS PAGE

  • Details of sensor test results
  • Top: SSID’s/Ethernet networks configured
  • Default view 24 hour: results stored 30 days. (top right)

STATUS

  • Detailed results collected by sensor (specific time selected)
  • Lock(click) on error the graph, this will lock to that timeframe revealing that error. It also locks WiFi, Network, Internal etc.(drag to zoom over)
  • Ongoing: Issue detected sensor trying to replicate to confirm the root cause
  • Resolved: Issue is resolved, (see the end time)

WIFI, NETWORK, INTERNAL and EXTERNAL 

  • Easily view impacted services if a particular threshold was missed 
  • Lock in on a specific timestamp all test will lock in identically
  • Provides metrics specific to an event with this sensor (+ to expand testing details)

ACTIONS
More information regarding the error will show(triage steps taken)

  • Download Data: pull data anytime from the sensor(bottom page)
  • Packet capture capabilities. (can be disabled)

On-Demand PCAP INFO 

  • Rolling buffer 50 MB ~ 6-10 min; 256 bytes; radiotap header + MAC header + data frame (encrypted) 
  • Cache on sensor: Manual request sensor uploads that buffer making it available through the dashboard
  • Automatic PCAP – packets transmitted between sensor & AP are available in ENHANCED ISSUE ANALYSIS (triage) page
  • PCAP for wired is not available as yet - look out for it in the near future

ABOUT 

Sensor details shows you how the sensor is connected to your network

WIFI ENVIRONMENT 

  • View of all SSID’s seen in the last 24 hours by the sensor
  • Filter SSID’s, signal strength etc 
  • Could reveal channels issues or unknown
  • Blue - BSSID being tested
  • Green - just tested
  • White - configured to test
  • @ Meta Data
  • Click the lock to quickly lock a BSSID for specific BSSID testing 

"Back to STATUS"

ENHANCED ISSUE ANALYSIS/TRIAGE

The sensor is continually testing the network, network services and applications and reporting the results back to the dashboard.  From the STATUS Page you can navigate to details about test results.  Click alerts below STATUS to reveal detailed test process taken to determine there is an issue

  • The dashboard reveals two types of alerts: 
  1. Alerts generated by a rolling average of measured data samples when crossing a threshold
  2.  Alerts generated by the sensor when it was not successful in executing a particular test. When this happens, the sensor will attempt to diagnose why the test failed in an automated triage mode
  • Triage mode runs a set of predefined tests based on the error reported by the original test
  • Triage will attempt to reproduce an issue seen on the same network as when it first encountered the error
  •  + Reveals details of step-by-step process similar to a field tech troubleshooting
  • Note actions like primary secondary DNS tries, failed iperf etc
  • PCAP file tagged to a specific error for up to 30 days.Provides time stamped details specific to the error
  • If the original issue was encountered on the wireless network, the sensor will attempt to recreate the issue on the wired network
  • Note time taken at each step is displayed

"Back to the Dashboard"

Did this answer your question?