Sign in
Get Help

Getting started with Automation Workflows for RMM


VSA 10 offers the option to build automated workflows, which will be triggered when a certain event occur from your monitored systems and that triggers a notification, allowing you to remedy some issues automatically.

Creating Workflow

1. Open VSAX WebApp -> Automation -> Workflows -> Create Workflow



2. Give the Workflow a name, activate it, set a maximum execution time and then click on the button 'Next' button.



3. On the next page, you will have the option to select a trigger type (Notification). In the example below, a High CPU Usage notification will be triggering the workflow when it exceeds preset limits.


Once a Trigger is selected, this is how it is displayed as part of the Workflow schema -



4. Once a trigger is selected, you will see the option to add a step in the chain of actions. Click on the "New Step" button to proceed.



5. A drop-down list will show up presenting available actions for the selected trigger.



You can make use of Condition steps to execute different actions based on the outcome of your logical statements.



For this example, we have setup a condition that if the High CPU usage notification on the system triggers and the name for the top process is Sublime, then the process should be killed.



In the screenshot above, we can see that there are options to add more actions based on the outcome from my first action. If the first action was successful, then under the green circle (on the left hand side) we can add additional conditions and actions. However, if the first action was not successful, then we can add more actions under red circle (on the right hand side) to add additional steps which to perform to remedy the issue.


Once all conditions are set, then we click on the button 'Create' at the right bottom corner and this task will be created


Here is an example how your workflow should look.


In this workflow, we add conditions so we can restart certain service on one particular system. If the condition 'System name' is equals to 'btserv' is removed then the action to start service will be executed on all systems in the group ESXi.


In order to start required services in required groups, these blocks with conditions should be chained as 'IF' statements.



Once the conditions are configured, the "Actions" can be set-up - that is, action to be performed when the condition is true (Start Service in the example below) and action to be performed when the condition is false.


To define these actions, simply click on the green circle or the red circle (indicating that the condition is true or false respectively).



Editing Workflows

In case you want to deactivate or edit any of these Workflows, then this option is available for you once you hover over the workflow entry with a cursor.



Once the Workflow is open for editing, in the "Details" section you may change the status, status and maximum execution time. In the "Workflow" section, you can make changes to the Workflow itself (triggers, conditions and actions). Once the changes are made, click on the button 'Save' to save the workflow.



Workflow Execution history

This section will show the Workflows' triggering timestamps and system on which they were triggered.



Have more questions?

Contact us

Was this article helpful?
0 out of 0 found this helpful

Provide feedback for the Documentation team!

Browse this section