1. Home
  2. IT Alert Management Software
  3. PagerDuty Reviews
  4. User Review of PagerDuty
Great flexibility and availability to achieve your alerting goals
December 16, 2022

Great flexibility and availability to achieve your alerting goals

Anonymous | TrustRadius Reviewer
Score 10 out of 10
Vetted Review
Verified User

Overall Satisfaction with PagerDuty

Pagerduty is used both for alerting teams to application problems that are identified by our monitoring and observability platforms as well as engaging on-call resources into an active incident bridge for real-time troubleshooting and remediation.
  • managing on-call schedules
  • providing multiple ways to trigger an escalation policy
  • providing multiple ways to configure escalation to additional responders
  • allowing the user to configure how they want to be contacted
  • enforcing governance around timing between levels on an escalation policy
  • enforcing governance around numbers of levels on an escalation policy
  • enforcing governance around how users configure their contact methods
  • PagerDuty is always available
  • it has a robust set of APIs
  • it allows for teams to self-manage their conifguration
  • application teams are able to own the support of their applications from dev through production
  • centralizing on how alerts are delivered from the observability platforms to the teams made it easy to onboard new team members
  • we know know who is oncall and can reach the right person for thousands of apps across our environment
Reliability is critical to my organization. Ensuring that PagerDuty is available when we're in a crisis means that we can get a hold of the right people to help manage our crises. If PagerDuty were to experience an outage at the same time as my organization, this would be a significant problem.
The pre-built integrations that PagerDuty provides made adoption and integration into our current environment extremely easy and efficient. The API-based custom integrations makes it possible for us to use PagerDuty everywhere we want to.
We do not leverage the incident response of rundeck's runbook automation.
We have thousands of disparate applications sending alerts into PagerDuty. Because of the disparate nature of the application alerts, we haven't been able to harness the power of PagerDuty's analytics.
PagerDuty seemed to have a much more flexible setup that allowed the organization to build and manage how we respond to alerts and incidents. The ServiceNow product seemed to be a bit more rigid.

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

PagerDuty is very flexible allowing users and teams to manage who is oncall, and for what escalation policies. It also provides a very robust set of APIs that allows the organization to do just about anything you can do from the PagerDuty UI. While the flexibility is great, and the API would effectively allow an organization to enforce whatever governance it wanted on how it's teams leverage PagerDuty, it doesn't have much governance out of the box. If an organization doesn't have a robust engineering team, and they want governance over how things are configured, PagerDuty may not be the solution for them. There also may not be any better options in the market.