Files
nexus/sreweekly/markdown/95/08-on-call-horror-story-number-three-this-wins-the-most-grueling-award.md
2026-09-12 17:23:01 +08:00

18 lines
1.3 KiB
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.
# On-Call Horror Story Number Three: This Wins the Most Grueling Award
- **期号**: SRE Weekly Issue #95(2017-10-29)
- **作者**: This article is published by my sponsor, VictorOps, but their sponsorship did not influence its inclusion in this issue.
- **链接**: https://victorops.com/blog/call-horror-story-number-three-wins-grueling-award/
## 简介
Grueling is right: their entire team came to the office over the weekend to work on the outage. Lesson learned:
> When something goes horribly wrong, don’t bring everybody in. More ideas are good to a point, but if you don’t solve it in the window of a normal human’s ability to stay awake, the value they are giving you goes down exponentially as they get tired.
## 正文
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.