Scheduler Extensibility Points

In the Turbo360 scheduler we have added some extensibility points where you can have the code-less automation call out to your own code to execute a custom extensibility point.  This opens up a range of new powerful opportunities.

The extensibility points are referred to as “Actions”.  They are available at 2 levels:

• Schedule level

• Resource level

The actions can also be configured to happen before and after activities happen too.

Example Scenario

Imagine where you have a scenario where you would like to achieve the following:

1. Before the schedule runs to turn off my VM’s I would like to integrate with my monitoring software to turn off a monitoring group

2. Before the schedule will execute a shut down command on my VM I would like to execute a Powershell command to safely shut down some services on my virtual machine

3. After my VM is started up I would like to execute some Powershell on the VM to log an event to the event log

4. After my schedule is complete and has restarted all of my VM I would like to turn on my monitoring software again

All of these types of scenarios can be implemented with the extensibility points.

Design Approach

In the Turbo360 scheduler we took the design approach to integrate from the scheduler to an HTTP endpoint.  This will allow you to integrate with a Logic App or Azure Function or other similar technologies.  We believe that you would prefer the code for your custom extensibility point to be held in your control and this is a safe way to integrate but also offers high flexibility.

Another good scenario would be if Turbo360 called your Logic App and then your Logic App could trigger an Azure Automation Runbook.

Adding Extensibility Point to Turbo360 Scheduler

Schedule Level

At the schedule level you are looking for the Configure Actions button as shown below.

Resource Level

At the resource level you want the list of resources and then the configure link.

Configuring the Action

On the configuration form you have the option to configure before and after actions.  You will need to turn then on with the radio button and then provide the details for the connection to your HTTP endpoint.

Some other points to note here include:

• You can also supply things like a description where you might indicate which Logic App you are calling.

• You can supply additional HTTP headers or a message body if you want to

Samples

In the below pages we have places some examples with starter kit Logic App templates which you can use to help you easily setup some of the scenarios I have discussed above.  You would simple copy the Logic App json template from the relevant page below and add it to your Azure Logic App then you can plug the extensibility into the Turbo360 scheduler.

• Schedule Level Examples

  • Before Schedule Runs Logic App

  • After Schedule Runs Logic App

• Resource Level Examples

  • Before Resource Runs Logic App

  • After Resource Runs Logic App