Daily Usage Test

Zoom license comes with limits on number of users, number of meetings which can be hosted, as well as participants in a meeting. That's the reason it is important to monitor the usage of Zoom account on daily basis so that administrators are aware of the current position with respect to limits and how to control the usage so that it doesn’t exceed the limits.

This test monitors the usage of the Zoom account and reports key the metrics like number of meetings, total meeting minutes, new users added etc.

The detailed diagnosis of this test also provide the details like Host, Email, Meeting Topic, Start time, end time etc.

Target of the test : Zoom

Agent deploying the test : A remote agent

Outputs of the test : One set of results for the Zoom account being monitored.

Configurable parameters for the test
Parameters	Description
Test period	How often should the test be executed, the default value is 12 hrs.
Host	The host for which the test is to be configured. By default, this is Zoom.us.
Client ID	When configuring the Zoom API, you should have created an API client with OAuth authentication. Each client app is assigned with a Client ID which you need to copy from client app configuration wizard and save down. Zoom API requires Client ID and Secret Token when calling REST APIs. To know more about how to create Client ID and Secret Token, refer to Setting up Zoom API
Client Secret	Secret Token is generated along with Client ID during API configuration. Each client app is assigned with a Client ID which you need to copy from client app configuration wizard. Zoom API requires Client ID and Secret Token when calling REST APIs. To know more about how to create Client ID and Client Secret, refer to Setting up Zoom API
Authorization Code	Authorization Code acts as an access token which tells Zoom on subsequent requests that current client has already been authorized. The Authorization Code is sent to client as string along with redirect URL once the client request has been authorized. In this text box, you need to specify the authorization code that you obtained during API configuration. For more details, refer to Setting up Zoom API
Redirect URL	In the authorization flow, the Zoom API request is first passed on to Zoom Auth Server. Once the authorization is successful, the client request is redirected back to URL provided by user in Redirect URL along with authorization code. Client can now hit the API with given authorization code to pull metrics.
API URL	Zoom offers globally accessible URL for Zoom REST APIs. To enable the eG agent to connect Zoom REST APIs and pull out metrics, this test should be configured with the accessible URL against this parameter. The default value of this parameter is https://api.zoom.us/v2/. Before using the APIs, first you need to create an API client, set up the authentication and authorization details as elaborated in topic Setting up Zoom API.
Show N DD	By default, this parameter is set to 50. This indicates that, by default, the detailed diagnosis of this test will display the details of only 50 events. If you wish this test to report details of all events, then specify "all" against this parameter.
Proxy Host and Port	If the eG agent need to communicates with Zoom via a proxy, then, you also need to configure the eG agent on the connector with the proxy server details. This will enable the eG agent to connect to the Zoom without a glitch, and pull metrics. To facilitate this communication. do the following: Specify the IP address/fully-qualified host name of the proxy server, against PROXY HOST. Specify the port at which the Proxy server listens for requests from the eG agent, against PROXY PORT. By default, both these parameters are set to none, indicating that the eG agent does not communicate with the Zoom via a proxy.
Proxy User Name and Password	Specify the Proxy username and password if proxy server is being used to connect with Zoom.
Confirm Password	Confirm the password by typing it in Confirm password box.
DD Frequency	Refers to the frequency with which detailed diagnosis measures are to be generated for this test. The default is 1:1. This indicates that, by default, detailed measures will be generated every time the test runs, and also every time the test detects a problem. You can modify this frequency, if you so desire. Also, if you intend to disable the detailed diagnosis capability for this test, you can do so by specifying none against DD Frequency.
Detailed Diagnosis	To make diagnosis more efficient and accurate, the eG Enterprise embeds an optional detailed diagnostic capability. With this capability, the eG agents can be configured to run detailed, more elaborate tests as and when specific problems are detected. To enable the detailed diagnosis capability of this test for a particular server, choose the On option. To disable the capability, click on the Off option. The option to selectively enabled/disable the detailed diagnosis capability will be available only if the following conditions are fulfilled: The eG manager license should allow the detailed diagnosis capability Both the normal and abnormal frequencies configured for the detailed diagnosis measures should not be 0.

Measurements made by the test
Measurement	Description	Measurement Unit	Interpretation
Meetings	Indicates the total number of Zoom meetings that happened today in current account.	Number	If the number of meetings is very large, and each meeting spans long time, administrators need to investigate the same further. The detailed diagnosis of this measure provide the details like Host, Email, Meeting Topic, Start time, end time, duration, participants, in room Participants, Has Voip, Has 3rd party audio, Has video, Has screen share, has recording, has pstn, Has archiving, Has sip, Audio quality, Video quality, Screen share quality, User type, Department, Meeting Id, Meeting UUID, As On.
Meeting minutes	Indicates the total number of minutes aggregated for all meetings.	Number	If the amount of time being spent in meetings is too high despite having small number of meetings, it might mean that meetings are not held efficiently.
New users	Indicates the total number of new uses who are participating in the meetings for the first time.	Number	If there are too many new users are getting added and joining the meetings, it might affect future meeting percentage.
Participants	Indicates the total number of meeting participants across all meetings.	Number	The detailed diagnosis of this measure provide the details like Participant name, Participant Email, Topic, Start Time, End Time, Duration, Leave reasn, User type, In room partipants, Has recording, Audion quality, Video quality, Screen sare quality, Domain, PC name, Device, Microphone, Speaker, Connection type, Network type, IP address, Location, Version, Data centre, Full data centre, From SIP URI, Share Application, Share Desktop, Share whiteboard, Participant ID, Participant user ID, Meeting ID and Meeting UUID.

The detailed diagnosis of this measure provide the details like Host, Email, Meeting Topic, Start time, end time, duration, participants, in room Participants, Has Voip, Has 3rd party audio, Has video, Has screen share, has recording, has pstn, Has archiving, Has sip, Audio quality, Video quality, Screen share quality, User type, Department, Meeting Id, Meeting UUID, As On:

Figure 1 : Detailed diagnosis of Meetings measure

The detailed diagnosis of this measure provide the details like Participant name, Participant Email, Topic, Start Time, End Time, Duration, Leave reasn, User type, In room participants, Has recording, Audion quality, Video quality, Screen share quality, Domain, PC name, Device, Microphone, Speaker, Connection type, Network type, IP address, Location, Version, Data center, Full data center, From SIP URI, Share Application, Share Desktop, Share whiteboard, Participant ID, Participant user ID, Meeting ID and Meeting UUID:

Figure 2 : Detailed diagnosis of Participants measure