Home » Orchestrator » Validate your runbook design – part V


Welcome to contoso.se! My name is Anders Bengtsson and this is my blog about Azure infrastructure and system management. I am a senior engineer in the FastTrack for Azure team, part of Azure Engineering, at Microsoft.  Contoso.se has two main purposes, first as a platform to share information with the community and the second as a notebook for myself.

Everything you read here is my own personal opinion and any code is provided "AS-IS" with no warranties.

Anders Bengtsson

MVP awarded 2007,2008,2009,2010

My Books
Service Manager Unleashed
Service Manager Unleashed
Orchestrator Unleashed
Orchestrator 2012 Unleashed
Inside the Microsoft Operations Management Suite

Validate your runbook design – part V

I have updated the Orchestrator Community Runbook Check again. The last version was unbelievable slow. It seems like every time the runbook invoke another runbook it took at least five seconds, operations that took one second if I keept it in the same runbook. For that reason I have added activities to a number of runbooks, instead of using library runbooks. I have also re-written a couple SQL queries to make things a bit faster, and added 0 rows result. It now takes around 15 minutes in my sandbox, instead of two hours.

I have also added one check to see if there is any delays configured on links and another check to list runbooks that are checked out during the check.

You can download the new version of the runbook, Orchestrator_Check_wolf_20110925. If you have any ideas what I should add, please post them as comment to this post or send me an e-mail.

Please note that this is provided “as is” with no warranties at all. Also please note this is all based on my ideas and is not a “Health check” or Microsoft official guidelines.

Leave a comment

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.