Page me, Scotty!
July 15, 2020
Page me, Scotty!
Score 9 out of 10
Overall Satisfaction with PagerDuty
It is being used to provide alerts for our business critical systems as well as notify staff of critical customer problems. So it is used by our DevOps team as well as Customer Success team.
- Schedules - Easy to schedule primary/secondary support.
- Escalation - Has a robust escalation mechanism.
- API - Has a good API which allows integration with existing tools.
- Notes made about an alert should be included in the alert. So then if you hand it off to another service they will see right away any notes which were made.
- The Incident page should let you search for an incident and filter incidents and not just enter a incident number.
- The UI can be a bit cumbersome.
- It is imperative that our services meet the SLA that our clients expect so it important in meeting our SLA.
- It is not inexpensive.
We require a very good SLA so we can keep the SLA with our clients. It is absolutely vital we are contact of potential problems before they affect our SLA.
We use Amazon AWS heavily so the integration with AWS is what we have used the most. We also use the API based so that diagnostic scripts can send a PagerDuty as needed.
We use the automated incident escalation to page other groups in our organization if the team receiving the initial alert does respond in the allocated time.
We selected PagerDuty because it makes the the job of handling a page simple and it is very reliable. It works and as a result we do not have to worry about getting an alert.
Do you think PagerDuty delivers good value for the price?
Are you happy with PagerDuty's feature set?
Did PagerDuty live up to sales and marketing promises?
Did implementation of PagerDuty go as expected?
Would you buy PagerDuty again?