Netreo Essentials is more than yet another monitoring tool. Users can configure Netreo Essentials to execute Actions on a resource automatically according to a schedule, including common maintenance activities.

For example, a Netreo Essentials customer can configure it to perform such Actions as automatically restart and shutdown VMs at a certain time or automatically delete old backup files.

If you have a scenario not covered by the article below, please open a support ticket with the Netreo Essentials team at to receive additional support.

Action scheduling is available to all plans during the initial trial period. After that, it is available only in the Ultimate plan.

Selecting Actions

To make an Action run automatically on a schedule, first the Actions must exist in a resource's configuration dialog. Locate the Action in the Actions tab of the resource configuration dialog or add it if it is not there.

Every resource has a predefined list of commands that can be selected for an action. All commands available for a given resource type are listed in the dedicated Configuration page for that resource. For example, Azure Windows VMs include commands that allow for rebooting, starting, shutting down, resizing and deallocating VMs.

Refer to the Automating Actions article to learn more about the basics of Actions.


Scheduling Custom SQL Actions and PowerShell Scripts

With Netreo Essentials Actions users can execute custom SQL scripts on relational databases (SQL Server, SQL Azure, MySQL, Oracle, etc.) to perform a variety of activities, such as update indexes, clean up tables, generate reports, etc.

When using the Netreo Essentials agent, it is also possible to execute predefined custom PowerShell scripts to perform a variety of additional activities, such as automatically archive log files, clean up temp folders, generate reports, etc.

Scheduling Actions

Actions are scheduled by selecting an available defined schedule for that Action in the Actions tab of a resource's configuration dialog. Schedule definitions are maintained on the Schedule Definition Screen (found in the Account Settings sidebar menu), but may also be added directly from the Action definition.


The simplest schedule causes an Action to execute 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 a.m., on the third day of every month, or every second Saturday in January, March and May.

Please refer to the Schedule Definition Screen to learn more about Schedules.

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.

A Schedule is only active if it’s assigned to at least one resource.