Initially, I started using it for managing on-call schedules. As the tech stack developed, we began using it for service alerts and event routing, and then transitioned to operational views and dashboarding. It eventually became central to our alerting systems, where all monitoring tools would send information to PagerDuty, enabling event management and routing to whoever was on call.

PagerDuty Operations Cloud
PagerDutyExternal reviews
External reviews are not included in the AWS star rating for the product.
Best for Incident Management
- Seamless Integrations
- Customizable Escalation Policies
- Ease of Setup and Use
- Limited Reporting Features
- Alert Noise and Latency
- Post-Incident Analysis Gaps
Best incident management tool ever
calling function,
tracking,
easy integration with slack,
service management,
automation action
shift management
Must have tool for incident managemnt
PagerDuty is so awesome product that nobody wants to get notified of any alerts in system
PagerDuty bailed me out in mission critical services
Reliable alerting platform to ensure operations continuity
one of the best incident management tool
Centralized alert management with customizable routing and superior scheduling
What is our primary use case?
What is most valuable?
The product used to be unique in getting the message to the right person to fix the job. It integrates with multiple applications and is highly customizable, with policies, escalation procedures, and an event routing tool that ensures contacting the right person. A significant advantage is that it includes a metrics overlay, which provides an overview of what is happening in the environment, and its scheduling capabilities are superior to other operations.
What needs improvement?
Everything can always be better. Operations are somewhat limited by their integration package. For example, integrating with Jira was problematic until they updated to a better plug-in. The ability to build customized modules would be advantageous, allowing organizations to define their own integration modules. It would be useful to have a way to define all configurations in code that is similar to how Terraform operates.
What do I think about the stability of the solution?
The solution has been 100% stable with no issues due to PagerDuty.
What do I think about the scalability of the solution?
The product was highly scalable, with no limits on the number of applications or event routing rules. However, managing a large number of these became cumbersome, suggesting a need for a way to define everything in code.
How are customer service and support?
The customer service was amazingly good. They helped us build our event routing.
How would you rate customer service and support?
Positive
How was the initial setup?
The setup is very straightforward, allowing users to be up and running within minutes. Usually, one knowledgeable person is enough to manage it.
What's my experience with pricing, setup cost, and licensing?
The solution was expensive, but if all its features were utilized, it was considered worth the cost. The tier-based pricing model was cumbersome, and there was a desire for a service-based catalog to better customize purchases.
What other advice do I have?
I'd rate the solution ten out of ten.
Enables us to bifurcate teams and redirect alerts
What is our primary use case?
We use the solution for incident management.
What is most valuable?
PagerDuty helps you bifurcate teams and redirect alerts to specific teams. It has good user management and is easy to plug in. It has good APIs to integrate with our apps and send alerts, making it compatible with most applications. It becomes a powerful infrastructure when handling priority applications, so we use it during the critical phase of our engineering development.
What needs improvement?
It is difficult to send underlying trace files or statuses using PagerDuty. You can set up email alerts, but you cannot build any triggers using those email alerts. There are limitations; you cannot extend it to send alerts to other teams. You can escalate it within the team but not redirect the alert to different teams.
How are customer service and support?
It has a good API for integrating with apps and good documentation. We seldom ask the support team for help. The app can call the on-call person even when the system is offline. It helps you handle alerts quickly, ensuring a fast turnover.
How was the initial setup?
It's straightforward to set up for an organization. It is easy to integrate with our apps.
What other advice do I have?
Overall, I rate the solution a nine out of ten.
Relax You'll Be Paged When You're Attention Is Required
2. Customizable on-call schedule and escalation policies 3. Mobile app - helps stay connected on the go
2. Pricing 3. Not a very user-friendly UI
Solution: PagerDuty integrates with various monitoring and logging tools to automatically detect incidents and alert the appropriate personnel. It streamlines the incident response process, reducing the time it takes to identify and address issues.