Runbook
In a computer science system or network, a runbook is a routine compilation of the procedures and operations which the administrator or operator of the system carries out. Runbooks are often used in information technology departments of commercial companies and NOCs as a reference for system administrators. Runbooks can be in either electronic or in physical book form. Typically, a runbook will contain the procedures to begin, stop, and supervise the system. It can also contain descriptions for the handling of special requests and of contingencies. An effective runbook will allow other operators, with prerequisite expertise, to effectively manage and troubleshoot a system. Through runbook automation, these processes can be carried out using software tools in a predetermined manner.
Runbooks are typically created by top tier managed service providers. They include procedures for every anticipated scenario and generally use step-by-step decision trees to determine the effective course of action given a particular scenario.
Run Book Automation
Run Book Automation (RBA) is the ability to define, build, orchestrate, manage and report on workflows that support system and network operational processes. A run book process can cross all management disciplines and interact with all types of infrastructure elements, such as applications, databases and hardware.
According to Gartner, the growth of RBA has coincided with the need for IT operations executives to deliver and prove higher IT operations efficiencies including reducing mean time to repair (MTTR), increasing mean time between failures (MTBF) and automating the provisioning of IT resources. In addition, it is necessary to have the mechanisms to implement best practices (for example, implement and manage IT operations processes in line with IT Infrastructure Library ITIL), increase IT personnel effectiveness (for example, automate repetitive tasks associated with IT operations process) and have the tools to fully report on how the processes are executed in line with established policies and service levels.
Further reading
- Langston, Mark C. (2003). Documentation Writing for System Administrators. SAGE Short Topics in System Administration. USENIX. p. 42f.
{{cite book}}
: Unknown parameter|coauthors=
ignored (|author=
suggested) (help) (payment required)
See also
References
- IT Operations Run Book Automation, by David Williams, Gartner. May 4, 2007.