Item: PagerDuty
Rating: 7
Author: Verified User

Overall Satisfaction with PagerDuty

Use Cases and Deployment Scope

It is used by one team, for propagating alerts based on an on-call schedule, including escalations in case the first responder is unavailable. We feed it notifications from Nagios and mostly use the app to receive and tack the alerts.

Pros and Cons

Pros

Good rotation scheduling mechanism.
Very robust uptime and dependable.

Cons

The cost model is extremely prohibitive for DevOps where multiple users need relatively infrequent access.
Analytics have a lot of room for improvement.

Return on Investment

It was easy and inexpensive to set-up.
It became unbearable when we wanted to extend use to other teams but could not yet afford the high cost.

Alternatives Considered

OpsGenie

OpsGenie provides a much better cost model for our company, we can now add all the users we need and we are extremely happy with it. Also, their support is very responsive and migrating was pretty easy. Their bi-directional Nagios integration is also very useful.

Support Rating

I didn’t have to use it much, and when I did it was not very helpful as the report I needed could not be made.

Key Insights

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?

Yes

Did implementation of PagerDuty go as expected?

Yes

Would you buy PagerDuty again?

Other Software Used

Elasticsearch, Graphite, Kubernetes, Apache Kafka, HAProxy

Likelihood to Recommend

PagerDuty is less suited for cases where you have a lot of team members that could be part of rotations, but would not get many alerts each. It is not perfect for this due to the per-user cost model and extremely high price per user. It is good for very small teams, and maybe for large corporations, but there is a huge cost gap in the middle.

Comments

Please log in to join the conversation

PagerDuty is a good start