Account Events Test
Account is the primary unit of entitlement in Zoom. Every Zoom account is identified through an account Id that is generated when the account is created. There are below types of accounts that can be created in Zoom platform:
Master Account — A master account is set up by the Zoom on-boarding team. This cannot be created by any other means. A master account is created with a default user who is designated as the account admin or account owner. The admin privilege lets the admin completely control all aspects of that account.
Sub-account — A sub-account has a direct relationship to master and can be created either by the master account admin or through the Zoom API. Again, a default user gets created who will be the admin of the sub-account. As with master account, a sub-account is identified with an account id.
Users — A user account can be created by the account admin associated to master or sub. A user account is created in the context of master or sub — it always belongs to either one of them.
Given that all user management activities can be captured through the action on account, it is important to monitor the account activities, through which administrators will get insights around the usage of Zoom.
This test monitors the account activities by subscribing to account events and collects key metrics like numbers of events for sub account creation, profiles being updated, sub account being disassociated etc.
The detailed diagnosis of these measures also provide the details like Account Id, Owner Id, Operation, Operator, and further details of the event. These details help investigate the account related issues and can also highlight problems with recent updates.
Target of the test : Zoom
Agent deploying the test : A remote agent
Outputs of the test : One set of results for the monitored Zoom account
| 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 |
|
Secret Token |
Secret Token is created 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 |
|
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. |
|
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:
|
| Measurement | Description | Measurement Unit | Interpretation |
|---|---|---|---|
|
Sub account has been created |
Indicates the total number of events received, when event is published each time when a sub account is created either manually or through API. |
Number |
Given that each sub-account adds up to the cost, administrators need to be aware of number of sub-accounts created. The detailed diagnosis of this measure reveal more granular metrics like Event time, Account Id, Owner Id, Email, Operator and Operation. |
|
Account/Sub account profile updated |
Indicates the total number of events received, when event is published each time when a sub account is created either manually or through API. |
Number |
Administrator need to be aware of every profile change. The detailed diagnosis of this measure reveal more granular metrics like Event time, Account Id, Account name. Account alias, Account Support name, Account support email, Managed Domains, Old account ID, Old Account name, Old Account alias, Old Account Support name, Old Account Support Email, Old managed domains, Operator, and Operation. |
|
Sub account disassociated |
Indicates the total number of events received, when event is published each time when a sub account is created either manually or through API. |
Number |
If the sub account has been disassociated but not removed, administrators c an remove the sub account. The detailed diagnosis of this measure reveal more granular metrics like Event time, Account Id, Owner Id, Email, Operator and Operation. |
|
Account vanity url approved |
Indicates the total number of events received, when event is published each time when account vanity url is approved either manually or through API. |
Number |
The detailed diagnosis of this measure reveal more granular metrics like Event time, Account Id, Vanity URL, Operator and Operation. |
|
Account vanity url rejected |
Indicates the total number of events received, when event is published each time when account vanity url is rejected either manually or through API |
Number |
The detailed diagnosis of this measure reveal more granular metrics like Event time, Account Id, Vanity URL, Operator and Operation. |
|
Account's entitlements added |
Indicates the total number of events received, when event is published each time when account's entitlements are added either manually or through API. |
Number |
Administrators need to review all the newly added entitlement to ensure only valid entitlements are provided to sub-accounts. The detailed diagnosis of this measure reveal more granular metrics like Event time, Account Id, Operator and Operation. |
|
Account's entitlements removed |
Indicates the total number of events received, when event is published each time when account's entitlements are removed either manually or through API. |
Number |
Very important for administrators to know if the entitlements to the account have been removed as this can cause issues with users. The detailed diagnosis of this measure reveal more granular metrics like Event time, Account Id, Operator and Operation. |
The detailed diagnosis of Sub account has been created reveal more granular metrics like Event time, Account Id, Owner Id, Email, Operator and Operation.
Figure 1 : The detailed diagnostics of the Sub account has been created measure
The detailed diagnosis of Account/Sub account profile updated reveal more granular metrics like Event time, Account Id, Account name. Account alias, Account Support name, Account support email, Managed Domains, Old account ID, Old Account name, Old Account alias, Old Account Support name, Old Account Support Email, Old managed domains, Operator, and Operation.
Figure 2 : The detailed diagnosis of the Account/Sub account profile updated measure
The detailed diagnosis of Sub account disassociated reveal more granular metrics like Event time, Account Id, Owner Id, Email, Operator and Operation.
Figure 3 : The detailed diagnosis of the Sub account disassociated measure
The detailed diagnosis of Account vanity url approved reveal more granular metrics like Event time, Account Id, Vanity URL, Operator and Operation.
Figure 4 : The detailed diagnosis of the Account vanity url approved
The detailed diagnosis of Account vanity url rejected reveal more granular metrics like Event time, Account Id, Vanity URL, Operator and Operation.
Figure 5 : The detailed diagnosis of the Account vanity url rejected measure
The detailed diagnosis of Account's entitlements added reveal more granular metrics like Event time, Account Id, Operator and Operation.
Figure 6 : The detailed diagnosis of the Account's entitlements added
The detailed diagnosis of Account's entitlements removed reveal more granular metrics like Event time, Account Id, Operator and Operation.
Figure 7 : The detailed diagnosis of the Account's entitlements removed measure
