Evolution of Our PagerDuty Playbook: Fewer Alerts, More Uptime(goshippo.com)
goshippo.com
Evolution of Our PagerDuty Playbook: Fewer Alerts, More Uptime
https://goshippo.com/blog/evolution-our-pagerduty-playbook-fewer-alerts-more-uptime/
2 comments
Why is the time to acknowledge longer than the time to resolve? I would have expected the opposite.
As our system matured, we added redundancy in our core system components and split up non-core core systems. This allowed us to immediately deprovision malfunctioning servers, timeout misbehaving 3rd parties and/or fix-forward quickly, resulting in a really low TTR compared to our TTA (which is also pretty low in the recent months)