In the last article, I showed how you can run a few SQL queries to find some detailed information about IPs, runbooks and activities and their relationships in the database. In this article, I’ll focus more on running runbooks (Jobs). To start with, here’s a diagram of the relationships of the tables related to to running a runbook:
Knowing these relationships, you can now use this info to to build queries to get interesting info about jobs.
This could help you spot jobs that have stalled at at activity and might need manual intervention. Similar to this would be those jobs who have not sent a heartbeat in a while.
Maybe you want to get some statistical info about how many jobs you’re running to make sure you’re utilizing your infrastructure appropriately. Here’s a good one:
You can take these queries and build on them to find out even more details about what’s going on in your Orchestrator environment. I’ll provide some more examples involving cleaning up the database in the next article.
Hey Robert, I am looking for a query to show all runbooks that have monitor activities and their current status. We are seeing some runbooks don't start automatically after a server reboot.
Appreciate any help you can provide.