18 lines
1.2 KiB
Markdown
18 lines
1.2 KiB
Markdown
# Post-Incident Reviews Part Four: A Post-Incident Review Guide and Next Best Steps
|
||
|
||
- **期号**: SRE Weekly Issue #88（2017-09-10）
|
||
- **作者**: This article is published by my sponsor, VictorOps, but their sponsorship did not influence its inclusion in this issue.
|
||
- **链接**: https://victorops.com/blog/post-incident-reviews-part-four-a-post-incident-review-guide-and-next-best-steps/
|
||
|
||
## 简介
|
||
|
||
Here’s the last installment of Jason Hand’s digest version of his new eBook, Post-Incident Reviews.
|
||
|
||
> If I leave you with one take-away from this guide, it should be that every incident provides an opportunity for your team to be more prepared for the next one.
|
||
|
||
## 正文
|
||
|
||
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.
|