Zoom Node is a unified platform providing a centralized Web-based deployment, management, reporting, and troubleshooting framework designed to improve management efficiency for on-premise modules. Administrators can quickly and easily deploy, manage, and troubleshoot their servers and modules all from within the Zoom Cloud. 

This article covers:

• How to access the Zoom Node
• How to use the Zoom Node management portal
  • Services tab
  • Nodes tab
  • Agents tab
  • Alerting tab
    • How to add a new alert
  • Logs tab

Prerequisites for using managing Zoom Node modules and services

• Business, Education, or Enterprise account
• Account owner or admin privilege
• Zoom Node subscription

How to access the Zoom Node modules 

1. Sign in to the Zoom web portal.
2. In the navigation menu, click Node Management, then click Modules. 

Once in the Zoom Node management section of the web portal, admins can begin to deploy, manage, and/or troubleshoot modules and servers.

How to use the Zoom Node management portal

Services tab

Under the Services tab, Admins can view the currently deployed services on their Zoom Node servers. As well as viewing the services, Admins can manage the services including, updating, modifying service configuration, as well as starting, stopping, and restarting services.

By clicking on the name of the module, admins can view the statistics and logs for the module, as well as configure the module.

Nodes tab

Under the Servers tab, Admins can view the status of currently deployed Zoom Node Servers, add servers, create server groups, and any new servers that are still unconfirmed servers.

Clicking the Name of a server, allows Admins view the current status of the Node server including the server information (IP Address, OS, Status, Agent Version, and server resource usage), as well as the current services installed on the server (including the services’ status, CPU and Memory usage, and current service version), and even clone the server (installing a copy of the current services, including their configuration, on a new server).

Additionally, clicking on a service allow Admins to view the current status of the service, as well as view statistics for the service, and upload the logs files to the Zoom Cloud for viewing and troubleshooting.

Agents tab

Under the Agents tab, Admins can view the agents currently deployed, as well as the status of the agents. When deploying new Node servers and agents, Admins can monitor the agent installation from this page.

By clicking on More , admins can also Stop, Restart, and Reload processes. 

Clicking on the name of the agents allows viewing of the IP, Status, and Version of the agent, as well as Statistics and Action History can also be viewed. Additionally, Admins can download log files from the agent, as long as the agent is online and reachable.

Alerting tab

Under the Alerting tab, Admins can view any current and past alerts for their Zoom Node servers including alerts pertaining to the following:

• Server CPU alerts
• Server memory alerts
• Server disk alerts
• Process alers
• Docker CPU alerts
• Docker memory alerts

Additionally, admins can create custom alerts under the Settings tab.

How to add a new alert

Note: The options available will be dependent on the type of metric chosen for the rule.

1. Sign in to the Zoom web portal.
2. In the navigation menu, click Node Management then click Modules.
3. Click the Settings tab.
4. Under Alerting, click + Add Rules.
5. Under Basic Info, enter the following information:

• Name: Name of the rule.
• Description: Enter a brief explanation of the rule.
• Metrics: Select the metric you want the rule to monitor and alert on.

Under Add Triggers, enter the following information: 

• Target Groups: Select the server group the rule will be set for.
• Service Type: Select which service the trigger will be utilized for.
  Note: This option is only available when Process, Container, or Phone Type is selected in the Metrics field.
• Threshold: Select whether the trigger is a Fatal, Error, or Warn (warning). 
  Note: Admins can set how many times the rule is triggered before there is an alert (1-10 times).
• Condition: Select the condition for which the rule is triggered.

(Optional) Click Add a new trigger, to add an additional trigger.

In Recipients, enter the email addresses of the admins that will receive the alert.

Click Save.
Once the rule has been added, it will be listed under Alerting of the Settings tab.

Enable the rule to start receiving alerts based on the newly created rule.

Logs tab

Under the Logs tab, Admins can view the activity logs for the servers and services deployed.