Successfully used PagerDuty on teams with production support responsibilities
December 16, 2022
Successfully used PagerDuty on teams with production support responsibilities
Score 8 out of 10
Vetted Review
Verified User
Overall Satisfaction with PagerDuty
We used PagerDuty primarily to manage on-call rotations across multiple engineering and support teams and to route automated alerts to the correct people in correct engineering teams. We also used it occasionally to route urgent (24/7) customer support requests to the correct people in product support departments. Additionally PagerDuty escalated incidents when they were not acknowledged or resolved promptly, and we used it as a tool to analyze data about the causes of frequent issues.
Pros
- Managing on-call rotations
- Sending notifications for urgent issues
- Tracking data about incidents and our incident response
Cons
- Analytics — diving into the source of incidents
- Push notifications
- On-call rotation management
- Incident analytics
- allows us operate a 24/7 premium support product
- ensures that we respond promptly and efficiently to service delivery issues
- expensive cost for teams that don't have production support needs
I worked at one company that used VictorOps (now Splunk On-Call) and it was quite similar to PagerDuty. VictorOps had a smaller customer base and fewer integrations, so there was less information on the Internet about how to use it effectively, and I don't think its API was as easy to use.
Do you think PagerDuty delivers good value for the price?
Yes
Are you happy with PagerDuty's feature set?
Yes
Did PagerDuty live up to sales and marketing promises?
Yes
Did implementation of PagerDuty go as expected?
Yes
Would you buy PagerDuty again?
Yes
Comments
Please log in to join the conversation