CloudMonix is more than yet another monitoring tool. Instead of doing a lot of repetitive and boring tasks, professionals can configure CloudMonix to execute them automatically. CloudMonix also allows for scheduling common maintenance activities, which minimizes the need for manual work.
For example, CloudMonix customers can use it to automatically restart and shutdown VMs or to automatically delete old backup files.
Task scheduling is available in the Ultimate plan only or during the initial trial period.
If you have a nuanced scenario not covered by the article below, please open a support ticket with the CloudMonix team at http://support.cloudmonix.com.
What tasks can be scheduled?
The tasks are scheduled using CloudMonix Actions with the help of Schedules on the resource configuration dialog. Every resource has a predefined list of Actions that can be selected from the dropdown in the Actions tab in the Resource configuration dialog.
All Actions available for a given resource type are listed in the dedicated Configuration page for that resource. For example for Azure Windows VM the available Actions allow for rebooting, starting, shutting down, resizing and deallocating VMs.
Refer to the Automating Actions article to learn more about Actions.
Scheduling custom SQL tasks and PowerShell scripts
With CloudMonix Actions users can also execute custom SQL scripts on relational databases (SQL Server, SQL Azure, MySQL, Oracle, etc), in order to update indexes, clean up tables, generate reports, etc.
Additionally, when using CloudMonix agent it’s possible to execute predefined and custom PowerShell scripts in order to automatically archive log files, clean up temp folders, generate reports, etc.
How to define schedule?
Tasks are scheduled based on the schedule definitions associated with the specific action. Schedule definitions can be maintained on the Schedule Definition Screen but can be added directly from the resource dialog’s Action definition.
The simplest schedule allows to perform a certain task daily at the predefined time. However, it’s just as easy to define a schedule that will perform the same task only on weekends, every Monday and Wednesday at 2 am, on 3rd day of every month, or every second Saturday in January, March and May.
For example, with the following schedule a task will be executed every second Sunday in January, February and March:
One Schedule definition can be used by multiple resources. Therefore it’s easy to manage even large systems with multiple resources, and share configurations across different applications and projects.
The Schedule is only active if it’s assigned to at least one resource.
Refer to the Schedule Definition Screen to learn more about Schedules.