ishenwei/nexus
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

SRE weekly 所有文章

Browse Source
This commit is contained in:
admin
2026-09-12 17:23:01 +08:00
parent 409b40ddcb
commit af7633f9dc
8486 changed files with 4489990 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files

17
sreweekly/markdown/60/06-firefighting-is-a-team-sport.md Normal file
View File

@@ -0,0 +1,17 @@
# Firefighting is a Team Sport
- **期号**: SRE Weekly Issue #60（2017-02-20）
- **作者**: This article is published by my sponsor, VictorOps, but their sponsorship did not influence its inclusion in this issue.
- **链接**: https://victorops.com/blog/firefighting-team-sport/
## 简介
This week from VictorOps is nifty primer on structuring your team’s on-call and incident response. I love when a new concept catches my eye like this one:
> While much has been said about the importance of keeping after-action analysis blameless, I think it is doubly important to keep escalations blameless. A lone wolf toiling away in solitude makes for a great comic book, but rarely leads to effective resolution of incidents in complex systems.
## 正文
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.