The Stack Overflow podcast is back! Listen to an interview with our new CEO.
6

I can't imagine having only one person on-call at a given time. There are several reasons that the primary person could be unable to handle an issue - perhaps they are unable to receive alerts, they have limited Internet access for a period of time, they or a family member could be ill and they are unable to work yet the on-call rotation hasn't been updated ...


3

Yes! And consider a third and a forth person if you're large enough. Folks can get sick. Their phone might have run out of battery. They might be dealing with a major local power outage. Folks go on vacation and forget to update the pager schedule. All of that, and more, can be addressed in a more reliable way by having a timeout on ack'ing a page ...


2

Based on the PagerDuty documentation on Cloudwatch, it doesn't look like it's configurable: https://www.pagerduty.com/docs/guides/aws-cloudwatch-integration-guide/


2

The easiest way to build this would be to have some sort of metrics-based alerting system like Prometheus, datadog, etc. Those systems allow you to have a counter that gets incremented and you can see how many incidents happened in a given period of time on a pretty graph. Most metrics systems will tie nicely to PagerDuty for the alerting piece. Having ...


1

There are a number of things that I think it's important to know before going on-call: How to triage an issue. There should be a defined list of priorities with examples so that you can identify how serious a problem is. What the priority levels mean. Can you ack this and then go back to sleep? Who to contact post-triage. The on-caller's primary ...


1

Within the CloudWatch integration in PagerDuty, you can change the "Derive name from" field to something like "Alarm Description".


Only top voted, non community-wiki answers of a minimum length are eligible