This documentation is for WSO2 Stream Processor 4.2.0. View documentation for the latest release.

All docs This doc
||
Skip to end of metadata
Go to start of metadata

When you open the WSO2 SP Status Dashboard, the Node Overview page is displayed by default. To view information specific to an active manager, click on the required active manager node in the Distributed Deployments section. This opens a page with parent Siddhi applications deployed in that manager node as shown in the example below.

This page provides a summary of information relating to each parent Siddhi application as described in the table below. If a parent Siddhi application is active, it is indicated with a green dot that appears before the name of the Siddhi application. Similarly, an orange dot is displayed for inactive parent Siddhi applications. 

DetailDescription
GroupsThis indicates the number of execution groups of the parent Siddhi application. In the above example, the Testing Siddhi application has only one execution group.
Child AppsThis indicates the number of child applications of the parent Siddhi application. The number of active child applications is displayed in green, and the number of inactive child applications are displayed in red.
Worker Nodes

The number displayed in yellow indicates the total number of worker nodes in the resource cluster. In the above example, there are two worker nodes in the cluster.

The number displayed in green indicates the number of worker nodes in which the Siddhi application is deployed. In the above example, the Testing parent Siddhi application is deployed only in one worker node although there are two worker nodes in the resource cluster.

If you click on a parent Siddhi application, detailed information is displayed as shown below.

The following are the widgets displayed.

Code View

View (Example)

Description

This displays the queries defined in the Parent Siddhi file of the application.

This allows you to check the queries of the Siddhi application if any further investigations are needed based on the kafka diagrams and performance.
For detailed instructions to write a Siddhi application, see Converting to a Distributed Streaming Application.

For detailed information about the Siddhi logic, see the Siddhi Query Guide.

PurposeThis allows you to check the queries of the Siddhi application if any further investigations are needed based on the observations of the performance of the distributed cluster to which it belongs.
Recommended Action

Edit the Siddhi file if any changes that can improve the performance of the Siddhi application are identified.
For detailed instructions to write a Siddhi application, see Converting to a Distributed Streaming Application .
For detailed information about the Siddhi logic, see the Siddhi Query Guide.

Distributed Siddhi App Deployment

View (Example)

DescriptionThis is a graphical representation of how Kafka topics are connected to the child Siddhi applications of the selected parent Siddhi application. Kafka topics are represented by boxes with red margins, and the child applications are represented by boxes with blue margins.
PurposeThis is displayed for you to understand how the flow of information takes place.

Child App Details

View (Example)

Description

This table displays the complete list of child Siddhi applications of the selected parent Siddhi application. 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:

  • Group Name: The name of the execution group to which the child application belongs.
  • Child App Status: This indicates whether the child application is currently active or not.
  • Worker Node: The HTTPS host and The HTTPS port of the worker node in which the child siddhi application is deployed.
PurposeTo identify the currently active child applications.
  • No labels