Runbook Scheduling
Execute Runbooks repeatedly over time
Last updated
Execute Runbooks repeatedly over time
Last updated
Some use cases for runbooks are better suited to be run repeatedly without interaction such as monitoring the health of a service or checking the remaining capacity of a storage.
In those cases you can assign a schedule to a runbook and have Azure automatically run it for you at your desired schedule.
RealmJoin Portal allows you to assign schedules to runbooks as well as to manage and create schedules.
By default, not all runbooks are flagged as schedulable. This is meant to easily indicate which runbooks are useful on a scheduled basis and which runbooks should preferably be used interactively.
By default, runbooks having the suffix _scheduled are flagged as schedulable. You can overwrite this behaviour using Runbook Permissions.
If a runbook is flagged as schedulable, the "Schedule" button next to the runbook will become active.
The schedule dialogue allows you to choose a schedule and to configure the parameters for the runbook's execution. If the parameters are left empty, the runbook's defaults will be used.
RealmJoin Portal will show existing schedule-assignments when browsing the runbooks.
Azure Automation allows administrators to define custom schedules for runbooks. You can use RealmJoin Portal to manage existing Azure Automation Schedules or to create new ones.
You can add a New Schedule, Edit or Delete an existing schedule from here.
If no schedules exist yet, RealmJoin Portal will offer a Create default schedules button:
Pressing this button will create a default set ("Hourly", "Daily", "Weekly", "Monthly") of schedules as seen above.
When creating or editing a schedule, you can modify its name, description, start and end date/time and frequency.
Execution of the runbook will happen on the days defined by start-date and frequency.
For example: If you configure a weekly frequency with an interval of 1 week, starting on Thursday 9th of March 2023, then then runbook will be executed on every Thursday including and after 9th of march. Setting an interval of 2 weeks will make it run on march 9th and only every other ("every second") Thursday afterwards and so on.
The start-time defines at which time the execution will happen. Setting the timezone makes sure the time is interpreted accordingly.
Use the navigation on the left, selecting the Runbook Logs and got the Schedules tab.
