Kicking off SMA Runbooks from SCSM Part 4: Monitor for Multiple Runbooks

In the last blog post we reviewed how to monitor for a single runbooks in SMA. To take burden of your runbook worker service as well as efficiency you will want to monitor for multiple runbooks at the same time. To do this we are going to configure the base of the monitor the same as we did in the Creating the SMA Monitor post. This should give us a starting monitor runbook that looks like this.   The first thing that we are going to do is get the Run Book Activities in SCSM that are in progress and have not been run. To do this we are going to create a new runbook to gather these. The runbook will use the following PowerShell (copy paste version at the end of the post).   Now that we have a runbook to get the runbook activities for SCSM we will need one to get the SR that contain these runbooks. When we kick off the runbook to get the SR we will pass it the Activity ID so we will set this as a parameter at the start of the runbook. Next we will use the following PowerShell to get the Service Request (copy paste version at the end of the post).   Since we are passing a variable into an inline script in this workbook you will notice we are using the $using variable to pass the Runbook ID into the inlinescript instance. Now that we have both these runbooks created we can go back to our monitor runbook and start kicking of our rubooks! The first thing we are going to do in the while($true) loop is get our runbooks to kick off. To do this we are going to call our SMA runbook to get these and set them to a variable. The next step will be a foreach loop that will run for each activity kicking of the appropriate runbook. The first step in the foreach runbook will be to get the Service Request that relates to the runbook so we can use that information later in the runbook we kick off.   Now that we have our RB and SR information we can kick off our runbooks. To do this we will use a switch statement base of the runbook name. We can get the runbook name easily by using $RB.EXTSMARunbooks. The PowerShell will look like this.   Now if we put it all together we are monitoring for our runbooks and kicking them off! The final runbook will look like this.   Now that we have our monitors figured out we need to deal with failed runbooks and completing the runbooks. These will be covered in the next blog posts. As promised below are the Scripts Used in a copy paste format. Get SCSM Runbook Activities   Get SCSM Service Requests Final Monitor Runbook