Users Experiencing Impacted Meetings
Focus
Focus
Autonomous DEM

Users Experiencing Impacted Meetings

Table of Contents

Users Experiencing Impacted Meetings

View which users experienced meetings that were negatively impacted and the root cause of the poor performance.
Where Can I Use This?What Do I Need?
  • Prisma Access (Managed by Strata Cloud Manager)
  • Prisma Access (Managed by Panorama)
  • Strata Cloud Manager
  • Prisma Access license
  • Autonomous DEM license
  • Zoom QSS license
View a list of all the users who were impacted by any Zoom meeting that they attended throughout the organization. Click a User Name to go to the user's User Details page. You can filter the data in this table by selecting a filter from
. You can filter for the users who have the most minutes impacted by a particular root cause by selecting Root Causes from the filter.
The widget breaks down the root cause of poor performance if any along with suggested remedies. in the Zoom Poor Performance Root Causes table, you can see that the user's Local Network Performance is less than desirable and the root cause for that is the high LAN latency. The last column, Suggested Remediation, gives the user some tips on how to resolve the issue.
Zoom Poor Performance Root Causes
Service Delivery SegmentThe segment in the service delivery chain (such as the user's device, Internet, WiFi, Local Network) where the Zoom call performance degraded. The segments can be any of the following:
  • Device - high CPU, RAM
  • WiFi - signal noise and quality
  • LAN - packet loss, latency, and jitter
  • Internet - ISP performance due to packet loss, latency, and jitter
Root CauseThe cause within the service delivery segment for the performance degradation.
Impacted MinutesThe total number of Zoom meeting minutes that were impacted by poor performance.
Percentage of Poor Performing MinutesThe total percentage of the poor performing minutes with respect to the total minutes the user spent on all Zoom calls that he/she attended.
A poor-performing minute can have multiple root causes, so the number displayed in this column could add up to more than 100%. For example, if a poor performing minute has two root causes, it will be counted as two separate minutes.
Suggested RemediationSteps that the end user can take to resolve the issue if possible. If the scope of the issue resolution is outside the user's control, then suggest some steps that the user can take, such as contact their administrator.