16 lines
1.2 KiB
Markdown
16 lines
1.2 KiB
Markdown
# On-Call Ways and Means: A Developer’s Guide
|
||
|
||
- **期号**: SRE Weekly Issue #58（2017-02-05）
|
||
- **作者**: This article is published by my sponsor, VictorOps, but their sponsorship did not influence its inclusion in this issue.
|
||
- **链接**: https://victorops.com/blog/on-call-ways-means-developers-guide/
|
||
|
||
## 简介
|
||
|
||
> Bringing non-traditional Ops folks, including developers, on-call can be a tricky process. Initial reactions tend to be highly polarized, either total pushback and refusal, or a meek acceptance coupled with fear of the unknown. For the former, understanding the root of the refusal is useful. For the latter, providing clarity and training is important.
|
||
|
||
## 正文
|
||
|
||
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.
|