Lessons Learned from Cloud Ops
summary
Run books explain exact steps, guardrails and verification for incidents at Splunk, with disk‑space and config alerts accompanied by executable code blocks and screenshots that copy from Confluence, process diagrams made in Lucidchart, and a service portal fed into Jira for update requests. Authors track running counts—some procedures run hundreds or thousands of times—standardize prechecks, numbered procedures, and branches so teams follow one orchestration and reduce time to resolution.
AI-written summary · about
chapters (13)
- 0:00Start
- 2:08DevOps
- 3:33A runbook is a detailed set of instructions that describe how to accomplish a specific task.
- 4:16Runbooks are simple steps...
- 4:57with examples and notes...
- 6:31Runbooks... Solve problems
- 9:41Product Docs vs. Ops Runbooks
- 12:11The "Ops User" Persona
- 19:17Create Procedures and Checklists
- 20:27Diagram Often
- 22:04Highlight Process Branches
- 23:39Runbooks Are Living Things
- 26:09In Conclusion...
related talks
28mDo you Know a Runbook From a Flip Book?...
24mAutomate your CloudOps and Spend Less Time Doing Operations
35mHow to Cloud Ops Like a Boss
45mProactively Stabilizing Key Business Process for Hybrid Cloud
25mThe More You Know: A Guide to Understanding your Systems
05mDevOps and incident management: A recipe for success
22mBattles Wounds from a Cloud SRE.. And a few lessons
40mDistilled Abnormal DevOps Iterations