Using a remote node monitor allows the user to perform connectivity tests (to SSH, FASP, TCP or Aspera Orchestrator) for a particular remote node, on one or more selected ports.
Option | Description |
---|---|
Active monitor | If this check box is checked, the node monitor is created in active mode; this means that the monitor of the node polls for the status of the nodes when the monitor is active. |
Node monitor name | The name of the new monitor node. |
Remote node | The remote node on which the monitor is created. The dropdown list of available options is derived from all the remote nodes configured in Orchestrator. |
Port |
This field displays all the ports that were configured while configuring the remote node. For each port, the user can set the notification type (Alerts, Warnings, or Nothing) and the test type (FASP, SSH, TCP, and Aspera Orchestrator). When Aspera Orchestrator is selected for the test type, one orchestrator node can know the process statuses (for example, the statuses of engine, mongrels, workers, and so on) of another orchestrator node. Note: If no ports are configured in the remote node configuration,
the following ports are associated with the new remote node
monitor by default:
|
Suppress duplicate events |
If a monitor state doesn’t change for a while, this flag stops a notification from being generated at every check. |
Notification workflow | This option lists all the workflows present in Orchestrator. Select the one that will be triggered when the notification has to be sent. For example, an email notification workflow can be configured and assigned to the monitor. For all notifications, that workflow will be triggered with the status of the monitor. |
Notification text | The text content indicates some information on the monitor. For example, a monitor name can be provided in the notification text. This text will be embedded in all the notifications that are sent to stakeholders. |
Alert processing code | This is an optional input. When there are alerts on a particular node for the selected test, an alert processing code is executed, mostly in lieu of amending the situation that triggered the alert. |
Warning processing code | This is an optional input. When there are warnings on a particular node for the selected test, a warning-processing code is executed, mostly in lieu of amending the situation that triggered the warning. |