In a computer system or network, a runbook is a compilation of routine procedures and operations that the system administrator or operator carries out. System administrators in IT departments and NOCs use runbooks as a reference.
Runbooks can be in either electronic or in physical book form. Typically, a runbook contains procedures to begin, stop, supervise, and debug the system. It may also describe procedures for handling special requests and contingencies. An effective runbook allows other operators, with prerequisite expertise, to effectively manage and troubleshoot a system.
Through runbook automation,[1] these processes can be carried out using software tools in a predetermined manner. In addition to automating IT specific processes, the results of the runbook can be presented on-screen back to the user or Service Desk engineer.[2] Multiple runbooks can be linked together using a Decision Tree to provide users with interactive troubleshooting and guided procedures.[3]
IBM Runbook Automation helps DevOps and IT Operations management teams to simplify and automate repetitive tasks.
Automate the collection of key troubleshooting information into an easy-to-read, color-coded dashboard to quickly find where the issue likely resides.
SMEs can document and design conditional logic that guides less-experienced agents through best practice procedures that pull in pre-built automations that overcome common hurdles related to system access and permissions.