Creating a Script Monitor

Configuration options are described in the following table.

Option	Description
Timeout	Time in seconds to abort running the script if it does not respond with a valid exit code.
Run as	Stats reported include folders inside the folder.
Run as password	Password of the above user.
Refresh rate	Frequency with which the script stats should be updated in the Overview screen.
Suppress duplicate events	If a monitor state doesn’t change for a period of time, this flag stops a notification from being generated at every check.

The following example shows the configuration of a script monitor for a script located at /opt/aspera/scripts/test_script.sh on the node OrchestratorDemoServer. If the script needs to run locally, create a localhost node.