Orchestrator Health Checker

Rating:        Based on 5 ratings
Reviewed:  5 reviews
Downloads: 2081
Change Set: 31123
Released: Jul 23, 2013
Updated: Apr 10, 2014 by randorfer
Dev status: Stable Help Icon

Downloads

Application Orchestrator Health Checker 1.8.9.zip
application, 330K, uploaded Jul 23, 2013 - 2081 downloads

Release Notes

Current Version 1.8.9
  • Orchestrator Health Checker
    • It allows to monitor the SCOrch 2012 (RTM and SP1) environment as a whole allowing amoung several things:
      • to see running and queued up Runbooks (summarized or per Runbook Server)
      • Get information of each specific instance connecting it with its PID
      • Ability to Stop the Runbook Tree (child, grandchild, etc Runbooks) as well as per Runbook Server
      • To execute Administrative Tasks such as: Stop All Runbooks, Stop All Monitoring Runbooks (Runbooks which their namess start with “Monitor “), Clear Orphaned Runbooks, Customized Log Purge, Start All Monitoring Runbooks (by invoking a Runbook specified in the application config file)
      • To verify the health of the system and the database (index fragmentation, files’ sizes, rebuild index) as well as Log Purge trending
      • To audit the environment Runbooks created, modified, deleted and still checked out since a certain date.
      • Ability to update password on Activities. Just specifying the User ID, the application will update all occurrences on Activities within Runbooks (if the Activity is not configured, you can add it by editing ActivitiesInfo.xml. Also, ability to update password on Variables and Configurations however the old password will be required and it works as a "Search and Replace" looking for the old password and replacing it by the new one.
      • NEW: Search Variable usage in all Activities
      • NEW: Running Statistics to verify Runbook Server % of usage. Monitor and Ad-hoc Runbook count. Status of all Monitor runbooks.
      • NEW: Fixed small bugs
      • NEW: Filter main view by Runbook Server or Runbook Name
      • NEW: Added new admin options
      • And more!
    • How to configure it?
      • No installation is required!
      • Configuration is done through the Application Config File. You should specify the ConnectingString to your SCOrch Database (required) and your Web Service URL as well as Start Monitor Runbook’s runbook name (optional). Check included .config file for reference, you just need to replace the word “MyEnvironment” or “My Environment” by whatever name you want (It suppots multiple-entries):

<connectionStrings>
<add name="MyEnvironment_SCORCH_DB" connectionString="Server=SCORCH_SQL_SERVERNAME;Database=SCORCH_DB_NAME;Trusted_Connection=True;"/>
<add name="My Environment_SCORCH_DB" connectionString="Server=SCORCH_SQL_SERVERNAME;Database=SCORCH_DB_NAME;Trusted_Connection=True;"/>
</connectionStrings>

Reviews for this release

     
This tool rocks! Awesome work, able to view all the inner workings of all my orchestrator servers in one interface. Provides utilities for cleaning up the database, viewing the log purge history, Running "Monitor" runbooks, the list goes on and on. Easy to use, easy to get started with. Kudos to the developer!
by jcoryat on Dec 22, 2016 at 2:00 PM
     
Very invaluable tool. For those of you that can't get the Start all Monitors button to work I made a little write-up explaining how. http://scsm.guru/2016/03/05/orchestrator-health-checker/
by jvenuto on Mar 6, 2016 at 3:27 AM
     
Hello, this tool not work for me. I stop all runbooks but after i don't start all runbboks. Where is the problem?
by fjdima1 on Apr 21, 2014 at 12:36 PM
For this to work you have to already have your own runbook called Start Monitor Runbooks within the Runbook Designer that the Health Checker will automatically execute to start your monitor runbooks.
Reply by vnerdahl (Developer) on Apr 15, 2016 at 3:58 PM
     
I had updated the Orchestrator Health Checker.exe.config with the Orchestrator Server and DB name. When I started the Orchestrator Health Checker.exe, I got the following exception: ---------------- Microsoft .NET Framework Unhandled exception has occurred in your application. If you click Continue, the application will ignore this error and attempt to continue. If you click Quit, the application will close immediately. Object reference not set to an instance of an object.
by wyattwong on Apr 16, 2014 at 2:32 AM
     
Works great!
by vnerdahl on Jan 3, 2013 at 7:41 PM