Viewing Node-specific Pages

When you open the WSO2 SP Status Dashboard, the Node Overview page is displayed by default. To view information specific to a selected worker node, click on the relevant widget. This opens a separate page for the worker node as shown in the example below.

Status indicators

Thw following gadgets can be viewed for the selected worker.

Server General Details

View (Example)
Description	This gadget displays general information relating to the selected worker node.
Purpose	This allows you to understand the distribution of nodes in terms of the location, the time zone, operating system used etc., and to locate them.
Recommended Action	In a distributed set up, you can use this information to evaluate the clustered setup and make changes to optimize the benefits of deploying WSO2 SP as a cluster (e.g., making them physically available in different locations to minimize the risk of all the nodes failing at the same time etc.).

CPU Usage

View (Example)
Description	This displays the CPU usage of the selected node.
Purpose	This allows you to observe the CPU usage of a selected node over time.
Recommended Action	Identify sudden slumps in the CPU usage, and investigate the reasons (e.g., such as authentication errors that result in requests not reaching the SP server). Identify continuous increases in the CPU usage and check whether the node is overloaded. If so, reallocate some of the Siddhi applications deployed in the node.

Memory Used

View (Example)
Description	This displays the memory usage of the selected node.
Purpose	This allows you to observe the memory usage of a selected node over time.
Recommended Action	Identify sudden slumps in the memory usage, and investigate the reasons (e.g., a reduction in the requests recived due to system failure). If there are continous increases in the memory usage, check whether there is an increase in the requests handled, and whether you have enough memory resources to handle the increased demand. If not, add more memory to the node or reallocate some of the Siddhi applications deployed in the node to other nodes.

System Load Average

View (Example)
Description	This displays the system load average for the selected node.
Purpose	This allows you to observe the system load of the node over time.
Recommended Action	Observe the trends of the node's system load, and adjust the allocation of resources (e.g., memory) and work load (i.e., the number of Siddhi applications deployed) accordingly.

Overall Throughput

View (Example)
Description	This displays the overall throughput of the selected node.
Purpose	This allows you to assess the performance of the selected node in terms of the throughput over time.
Recommended Action	Compare the throughput of the node against that of other nodes with the same amount of CPU and memory resources. If there are significant variations, investigate the causes (e.g., the differences in the number of requests received by different Siddhi applications deployed in the nodes). Observe changes in the throughput over time. If there are significant variances, investigate the causes (e.g., whether the node has been unavaialable to receive requests during a given time).

Siddhi Applications

View (Example)
Description	This table displays the complete list of Siddhi applications deployed in the selected node. The status is displayed in green for active Siddhi applications, and in red for inactive Siddhi applications. In addition, the following is displayed for each Siddhi application: Age: The age of the Siddhi application in milliseconds. Latency: The time (in milliseconds) taken by the Siddhi application to process one request. Throughput: The number of requests processed by the Siddhi application since it has been active. Memory: The amount of memory consumed by the Siddhi application during its current active session, expressed in milliseconds.
Purpose	This allows you to assess the performance of each Siddhi application deployed in the selected node.
Recommended Action	Identify the inactive Siddhi applications that are required to be active and take the appropriate corrective action. Identify Siddhi applications that consume too much memory, and identify ways in which the memory usage can be optimized (e.g., use incremental processing).