Dashboard Panel: Delays

 

Related Article: How to Use The Engagement Analytics Dashboard

 

The main "Administrator" Dashboard contains four panels that relate to delays encountered due to poor connections/devices while in sessions.

  • Total Delayed Attendees - The number of Attendees affected by Poor connections (in all Sessions).

  • Average Delay - The average length of delay caused by poor connection/device performance (measured in milliseconds).
  • Total Device Delays -The number of Attendees affected by Poor connections during Sessions - reported from the Device.
     

  • Average FPS when Delayed - The average Frames Per Second (fps) of Attendees experiencing a delay (25 fps is normal) - reported from the Device.

 

 

Drill-Down to see "Delay Details"

Hover over the "i" (information) icon, then click on the link that appears... 

2019-01-03_12-19-06.png

 

Clicking the link will open the "Delay Details" drill-down dashboard....

 

2019-01-03_12-34-17.png

Any filters applied to the main dashboard will be inherited by this one.

This table can be exported to a CSV/Excel spreadsheet.

 

Important Notes: This table only show delay details...

  • For the last 30 days. If your date filter is larger than "Last 30 Days", you will still only see the last 30 days of details in this table. 

  • For delays that are 1,000 ms (1 second) or longer.

 

The "Delay Details" table is quite technical and will be most useful to technical people. Listed below is some helpful information about the data displayed...

1. The table shows one row for EACH delay experienced by a person in a session (of at least one second, within the past 30 days). So, if a person experienced 20 delays of at least one second in a session, there will be 20 rows for that same person/session. 

 

2. Jigsaw Interactive tracks delays from both the "Server side" and the "Client/Device side". Usually, the Server will be quicker to pickup on any delay going on, but if the delay is being cause by something specific on the Client side (like the device CPU is overloaded), we also report these delays. Regardless of which "end" of the application records the connection issues, the issues recorded/listed in this table are all due to customer-side connectivity issues.

 

3. Column Information

Session/Attendee - Information

(these columns show general information about the Attendee/Session)

  • Host Name
  • Session Name
  • Attendee Name
  • # Minutes (Entire Session)
  • # People (Entire Session)
  • Host? (Is the attendee the Host? 1 = Yes and 2 = No)
  • IP Address - Attendee's IP address
  • Device Type
  • O/S (Operating System)
  • O/S Ver (Operating System Version)
  • Browser
  • Browser Version

 

Session/Attendee - Totals

(these columns show delay information for the overall Attendee/Session)

  • # Total Delays - Total number of delays experienced by this Attendee during this entire Session.
  • Max Delay - the Maximum Delay experienced (in seconds) by this Attendee during this entire Session.
  • Avg. FPS - the Average Frames Per Second achieved by this Attendees Device during this entire Session. (reported from the Device)

 

Individual Delays (row level)

(these columns show delay information specific for EACH individual delay experienced by an Attendee, each "row" represents one delay)

  • Date/Time of Delay - The date/time of the delay.
  • Delay - The length of delay, in seconds.
  • Device Ping - The Ping Rate (in milliseconds) at the time of the delay. (reported from the Device)
  • FPS - The number of (frames per second) the user's device was capable of handling at the time of the delay. Normal = 25 FPS, anything less than 25 indicates a delay that is probably due to insufficient device processing power (CPU).
  • # Device Delays (1) - The number of device delays that were noted using our primary method. (reported from the Device)
  • # Device Delays (2) - The number of device delays that were noted using our secondary method. (reported from the Device)
  • # Client Conn Delays (1) - The number of connectivity delays that were noted using our primary method. (reported from the Device)
  • # Client Conn Delays (2) - The number of connectivity delays that were noted using our secondary method. (reported from the Device)

 

 

Was this article helpful?
0 out of 0 found this helpful