In the last three blog posts I showed you how to create three different types of Azure Automation monitors. Now we are going to look at the pros and cons of each so you can determine the monitor for you!
Monitor with Azure Automation Schedules
Creating a monitor using the Azure Automation Schedules
is very usfull in situations where you want to have a runbook run every 15 min. or more. If you start going into shorter times you will have lots of schedules attached to one runbook.
- All the pieces of the runbook are in Azure Automation.
- Visibility. It is very easy to see the schedule attached to your runbook
- In situations of hourly intervals you only need on schedual
- You can set the runbook to never expire
- Can use lots of schedules when going under 15 min. on your interval
Monitor using the Azure Job Scheduler
The Azure Job Scheduler
addresses the issue of having to many schedules when wanting to run your monitor at a higher interval. There is some trade off as you will now have more moving pieces.
- On schedule per runbook. Azure Job Scheduler lets you schedule as low as 1 min. intervals.
- All pieces still run in Azure
- Multiple pieces with lower visibility. You now have a webhook and an azure scheduled job to watch.
- Expiration dates. Both the webhook and the scheduled job have an experation date.
Monitor using a Textual Runbook
The Textual Runook Monitor
allows you to create runbooks down to the second but comes at a cost! This monitor may be best suited for SMA.
- Allows you to create runbooks that run on any interval you want.
- Allows you to monitor for multiple things at once
- Lower visibiltiy on the runbook you are kicking off
- COST since the job is running all the time it will be costing you money. This may change depending on hybrid runbook workers but for now you are charged for either.