In Pulseway version 7.5 we have added the option to build automated workflows which will be triggered when certain events occur from your monitored systems and notification is triggered allowing you to remedy some issues automatically.
1. Open Pulseway WebApp -> Automation -> Workflows -> Create Workflow
2. Give the workflow a name, activate a task and then click on the button 'Next'
3. On the next page you will have the option to select the trigger type (Notification). In the example bellow a High CPU Usage notification will be triggering the workflow when it exceeds preset limits. (More triggers and actions are being added)
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've 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 'Save' 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 (add a new step [block of conditions] under the circle with red cross).
In case you want to deactivate or edit any of these tasks, then this option is available for you once you hoover over the task entry with a cursor.
Once task is open for editing you may change the status for the task, change the name and then click on button 'Next', edit conditions if required and then click on the button 'Save' to save workflow.
Workflow Execution history
This section will show when workflows were triggered and on which system