Monitoring

The individual nodes in the cluster can be monitored and managed. The following actions are available on the monitoring screen:

• Add nodes to the cluster

• Deploy configurations to the nodes in the cluster

• Deploy configurations to specific node groups

• Change groups in the cluster

• Change groups on selected nodes

• Refresh nodes in the cluster

• Start, stop, or restart individual nodes

The following figure illustrates the Monitoring screen:

1 Cluster Health - Cluster health indicator in Green, Orange, or Red.

2 Hostname - Hostname of the DSG.

3 IP - IP address of the DSG.

4 PAP version - Build version of the DSG.

5 Health - Status of DSG.

6 Node Group - Node group assigned to the DSG node. If no node group is specified, the node group is assigned as default.

7 Config Version - The tag name provided while deploying the configuration to a particular node group.

8 DSG Version - Build version of DSG.

9 Uptime - Time that the DSG has been running.

10 Load Avg - Average load on a process in the last five, ten, and fifteen minutes.

11 Utilization - Number of DSG processes and CPU cores utilized.

12 Connections - Total number of active connections for the node.

13 Select for Patch Installation or Node Group Update - Select the option to updating the node group

14 Socket - Total number of open sockets for the node.

15 Config Version Description - The additional information about the configuration version. If the description is not provided while deploying the configurations to a particular node group, then this field will be empty.

Cluster and node health status color indication reference:

Color	Description
	Node is healthy and services are running.
	Warning. Some services related to a node need attention.
	Not running or unreachable.

The following figure illustrates the actions for the Cluster Monitoring screen.

The callouts in the figure are explained as follows.

1 Expand - Expand to view the other columns.

2 Refresh - Refresh all the nodes in the cluster. The Refresh drop down list provides the following options:

• Start: Starts all nodes.
• Stop: Stops all nodes.
• Refresh: Refreshes details related to all nodes.
• Restart: Restarts all nodes. The restart operation will not export the configurations, it will only restart all the nodes.
• Deploy: Deploys the configuration changes on all the DSG nodes in the cluster. The configurations are pushed and the node is restarted. For more information, refer here.
• Deploy to Node Groups: Deploy the configurations to the selected node groups in the cluster. The configurations are pushed and the node is restarted. For more information, refer here.

3 Actions - The Actions drop down list at the cluster level provides the following options:

• Apply Patch on Cluster: Applies a patch to all nodes in a cluster including the ESA.
• Apply Patch on Selected Nodes: Apply the same patch simultaneously on all selected nodes.
• Change Groups on Entire Cluster: Change the node group of all the DSG nodes in the cluster
• Change Groups on Selected nodes: Select the node and change the node group on that particular DSG node in the cluster
• Add Node: Adding a Node to the Cluster.

4 Order - Sort the nodes in ascending or descending order

5 Actions - The Actions drop down list at the individual node level provides the following options:

• Start: Start a node
• Stop: Stop a node
• Restart: Restart a node.
• Apply Patch: Applies a patch to a single node. Before applying a patch on a single DSG node, ensure that the same patch is applied on the ESA.
• Change Groups: Changes the node group on an individual DSG node
• Delete: Delete a node.

Deploying the Configurations to Entire Cluster

The configurations can be pushed to all the DSG nodes in the cluster. This action can be performed by clicking the Deploy option on the Cluster page or from the Ruleset page.

To deploy the configurations to entire cluster:

1. In the ESA Web UI, navigate to **Cloud Gateway > 3.3.0.0 {build number}**Cloud Gateway > 3.3.0.0 {build number}> Cluster.

2. Select the Refresh drop down menu and click Deploy.

   The following pop-up message occur on the Cluster screen.

   

3. Click YES to push the configurations to all the node groups and nodes.

   The configurations will be deployed to all the nodes in the entire cluster.

Deploying the Configurations to Node Groups

The configurations can be pushed to the selected node groups. The configuration will only be pushed to the DSG nodes associated with the node groups. This action can be performed by clicking the Deploy to Node Groups option on the cluster page or from the Ruleset page.

To deploy the configurations to the selected node groups:

1. In the ESA Web UI, navigate to **Cloud Gateway > 3.3.0.0 {build number}**Cloud Gateway > 3.3.0.0 {build number}> Cluster.

2. Select the Refresh drop down menu and click Deploy to Node Groups.

3. Perform the following steps to deploy the configurations to the node groups.

   1. Click Deploy to Node Groups.

      The Select node groups for deploy screen appears.

      

      The default and lob1 are the node groups associated with the DSG nodes. When you add a node to cluster, a node group is assigned to that node. For more information about adding a node and node group to the cluster, refer here.

   2. Enter the name for the configuration version in the Tag Name field.
      The tag name is the version name of a configuration that is deployed to a particular node group. The tag name must be alphanumeric separated by spaces or underscores. If the tag name is not provided, then it will automatically generate the name in the YYYY_mm_dd_HH_MM_SS format.

   3. Enter the description for the configuration in the Description field. The user can provide additional information about the configuration that is to be deployed.

   4. On the Deployment Node Groups option select the node group to which the configurations must be deployed.

   5. Click Submit.