Runbook
A runbook is documented or executable operational guidance specifying procedures for performing repeatable tasks, operating or maintaining systems, or responding to incidents.
Practical Automation with PowerShell: Effective scripting from the console to the cloud
A runbook is an executable automation definition containing a script or workflow for performing operational tasks.
- How it is used
- Centralizes automation that can run in Azure or on hybrid workers against on-premises resources.
- How deep it goes
- Builds, imports, parameterizes, authenticates, tests, and logs a PowerShell implementation while deferring Azure Blob storage internals.
- Examples
- Demonstrates Upload-ZipToBlob uploading ZIP archives and deleting local copies, alongside output-stream and logging examples.
- What you can do after
- Build it from scratch: develop, import, parameterize, test, and run a PowerShell runbook through a hybrid worker.
Think Like a Software Engineering Manager
A runbook is documented operational guidance describing procedures for deploying, operating, troubleshooting, or recovering a system.
- How it is used
- Supports on-call maintenance and incident response by recording ownership, procedures, and resolutions to common customer problems.
- How deep it goes
- Defines runbook contents and explains their operational value, but does not provide a step-by-step runbook template.
- Examples
- Uses a repository of common customer problems and their resolutions as the concrete runbook example.
- What you can do after
- Diagnose/debug with it by consulting known resolutions, ownership, and alert-linked guidance during on-call incidents.
Read how Think Like a Software Engineering Manager explains runbook →
Machine Learning System Design
A runbook is an operational document containing procedures for diagnosing and resolving recurring system problems.
- How it is used
- Supports on-call rotations by turning recurring production failures into documented diagnostic, repair, and escalation procedures.
- How deep it goes
- Defines common fixes and escalation paths, but leaves broader failure learning to retrospectives and postmortems.
- Examples
- Uses instance scaling during spiky customer demand and escalation to vendors or senior leaders during outages.
- What you can do after
- Operate/configure recurring incidents by following repair recipes, scaling guidance, and explicit escalation paths.
Related concepts
- Azure Automationused by · Azure Automation is Microsoft's cloud service for automating recurring operational tasks across Azure and other environments.
- postincident analysisproduced by · Postincident analysis is a structured examination of an incident and its response to understand what occurred, identify causes, and determine improvements or corrective actions.
- incidentaddresses · An incident is an unplanned adverse operational event that disrupts, degrades, or threatens the normal functioning of a system, service, or process.
- shell scriptkind of · Bash is a Unix command-line shell and scripting language for executing commands interactively and through scripts.
These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.