Files
nexus/sreweekly/markdown/8/06-the-how-and-why-of-minimum-viable-runbooks.md
2026-09-12 17:23:01 +08:00

16 lines
919 B
Markdown
Raw Blame History

This file contains ambiguous Unicode characters
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
# The How and Why of Minimum Viable Runbooks
- **期号**: SRE Weekly Issue #8(2016-01-31)
- **作者**: —
- **链接**: https://victorops.com/knowledge-drop/devops-docs/minimum-viable-runbooks/
## 简介
VictorOps distilled their Minimum Viable Runbooks series (featured here previously) into a polished PDF in their usual high quality and style.
## 正文
VictorOps is now Splunk On-Call — new name, updated product. With Splunk On-Call, developers, devops and operations teams make on-call suck less while reducing mean time to acknowledge and restore outages. Teams receive context-rich notifications and collaborate cross-functionally to empower fast, efficient incident resolution with reduced downtime. Stakeholders can gain visibility to critical incidents and steps taken to resolve incidents.
Sign into your Splunk On-Call account, get user support or explore our other resources to learn more.