PagerDuty Reviews & Product Details

1.Our infrastructure foor print caters across AWS, Datadog, New Relic, and other tools. We used to have trouble monitoring all the application under different dashboards and with teams across th globe, this used to be very challenging.

2.PagerDuty has seamless integration with all the above services including Teams and Slack channels, enabled us a single point of source monitoring(dashboards) and response(its auomtaion capabilities) across 40+ accounts and 50+ microservices.

3.Its automated and priority-based notifications (emails, calls, messages) and dynamic on-call scheduling capabilities giving the option to notify the the right teams based on the service and ensure response instantly (Acknowledging via Phone call, message & email), reducing MTTR for critical services. All this can be done via Mobile App is an added advantage.

4.Its Built-in options for conference bridges for each service, configuring issue resolution guides, automation (Rundeck) to run primary health checks, service graphs enable global teams to troubleshoot together in real time, ensuring business continuity 24/7 which is priority for our business every single day.

5.Dashboards provide leadership with a clear view of service health, issue trends, and performance metrics, driving informed decisions and proactive improvements.

6. Learnign wise, Pagerduty university has lof of content to learn and certify. I have done Pagerduty Incident Responder course a7 certification for free. Review collected by and hosted on G2.com.

Automation tasks can be challenging sometimes, since we need to provide some manual input for certain services and thats how our design is.

While alerting is highly commendable, it often triggers too many notifications based on false alerts. We should have some solution in place to limit in certain amount of time. It all needs to be closed manually more often.

I really miss "Quick templates" feature where most of the toold provide. Since we need to configure everything from scratch, it does took us a lot of time (for new teams it will be challending). We should have something like starter kit to get going from Day-1. Review collected by and hosted on G2.com.

Reliable alerting

PagerDuty excels at getting the right alerts to the right people quickly through multiple channels like mobile app, phone, SMS, and email, which is crucial for reducing MTTR in production environments. Users consistently highlight that alerts are timely, granular, and dependable, which helps avoid missed incidents and supports 24x7 operations.​

On‑call scheduling and escalations

The on‑call management features make it easy to build fair rotations, escalation policies, and handoffs without manual spreadsheets or ad‑hoc processes. This structure improves accountability, prevents burnout, and ensures someone is always available to respond, which is especially valuable for global or follow‑the‑sun teams.​

Integrations and workflow automation

PagerDuty integrates with most major monitoring, logging, and ITSM tools, turning raw alerts into actionable incidents and routing them automatically. Automation capabilities (including AI-driven and runbook automation) can trigger diagnostics, remediation steps, and collaboration workflows, cutting noise and speeding up resolution.​

Collaboration and visibility

Incident dashboards, status updates, and post‑incident features give teams and stakeholders a shared view of what is happening during outages. This improves coordination across SRE, infrastructure, app teams, and management, and makes it easier to learn from incidents and improve reliability over time. Review collected by and hosted on G2.com.

PagerDuty's most common drawbacks include high pricing, a clunky user interface, and alert overload during incidents.​

UI and usability issues

The interface is often called unintuitive, overwhelming for schedule overrides, rotations, and configs, with extra steps for simple tasks like editing overrides (requiring delete/recreate). Mobile app notifications nag about settings, and setup complexity adds a steep learning curve, especially for non-experts managing on-call.​

Alert noise and reliability

Multiple rapid alerts can overwhelm phones with repeated calls, preventing acknowledgment and escalating stress during outages. While upstream monitoring fixes help, PagerDuty's lack of built-in noise reduction in lower tiers contributes to fatigue and morale hits for on-call staff Review collected by and hosted on G2.com.

I really appreciate how PagerDuty provides comprehensive visibility and control over our incident management process. Its real-time alerting is both reliable and quick, ensuring that the appropriate team members are notified instantly and without unnecessary distractions. The user-friendly dashboards, efficient on-call scheduling, and smooth integrations with our monitoring tools make it straightforward for teams to work together during incidents. Overall, PagerDuty enables us to respond more quickly, stay organized, and maintain high service uptime with minimal effort. Review collected by and hosted on G2.com.

One thing I dislike about PagerDuty is that the interface can feel a bit overwhelming at times, especially when navigating deeper configuration settings or managing complex on-call schedules. Some customization options also require extra steps, which adds to the learning curve for new users. Additionally, alert noise can build up quickly if not fine-tuned properly, making the initial setup a bit time-consuming. While the platform is powerful, simplifying certain workflows would make the overall experience even better. Review collected by and hosted on G2.com.

Real-time alerting provides immediate notifications for critical incidents, which helps reduce response times. The escalation policies ensure that if one engineer does not respond, the incident is automatically escalated to the next person, preventing incidents from being overlooked. On-call scheduling is straightforward, making it easy to manage rotation schedules and distribute on-call duties among team members. The integration capability is strong, as it works seamlessly with monitoring tools, ticketing systems, Slack, Teams, and various automation platforms. Incident timeline visibility is excellent, offering a clear view of the sequence of events, including who acknowledged the incident and what actions were taken. This setup helps reduce MTTR, as teams can respond more quickly and in a coordinated manner, leading to less downtime overall. Mobile app support is also available, allowing users to acknowledge and respond to incidents directly from their phones when they are away from their desks. Review collected by and hosted on G2.com.

Alert fatigue can be an issue, as the system sometimes generates an excessive number of alerts, many of which are not critical. This can make it harder to maintain focus and respond with the necessary urgency. Additionally, there is a lot of noise from duplicate or repeated alarms—if thresholds or integrations are not properly configured, the same problem may trigger multiple alerts, which can be distracting. The pressure of being on-call is also significant; during particularly busy periods, the constant stream of notifications can be stressful and negatively affect work-life balance. Configuring escalation chains, routing rules, and service dependencies can be complex, especially for new users, and is not always intuitive. Finally, the alerts themselves sometimes lack sufficient context, so you often have to consult monitoring tools or logs to get the full details, as the PagerDuty notification alone is frequently insufficient for diagnosis. Review collected by and hosted on G2.com.

I like PagerDuty because it ensures critical alerts reach the right people at the right time.

Its on-call scheduling and escalation policies help reduce downtime and respond to incidents quickly. Review collected by and hosted on G2.com.

PagerDuty can feel noisy at times, with too many alerts if rules aren’t tuned properly.

The interface and configuration can also be a bit complex for new users. Review collected by and hosted on G2.com.

Serves as a useful application for configuring alerts and monitoring key processes. The ability to set up an on-call rota and define clear escalation policies are great features. Review collected by and hosted on G2.com.

Nothing major for me, but I felt the interface was clunky and it took me a while to get used to the navigation. For a new user, it could be a daunting experience. Review collected by and hosted on G2.com.

PagerDuty makes incident alerts fast and reliable. It sends the right notifications at the right time and keeps our team organized. The on-call schedules are easy to manage, and the mobile app helps us respond quickly. It reduces downtime and makes our work smoother. Review collected by and hosted on G2.com.

PagerDuty can feel noisy at times when alerts are not filtered well. Some settings are a bit complex for new users. The pricing is also on the higher side for small teams. Overall, it works well but could be simpler and more cost-friendly. Review collected by and hosted on G2.com.

The on-call scheduling and the mobile app are the standout features. The scheduling engine is incredibly robust—handling complex rotations, follow-the-sun models, and last-minute overrides is seamless once the logic is set up. The mobile app is equally impressive; it’s intuitive, reliable, and allows for quick triage or acknowledgement of incidents without needing to open a laptop. It really nails the "responder experience" by putting critical actions front and center. Review collected by and hosted on G2.com.

I find the API and Slack integrations to be too rigid. While the Slack integration works well for basic "ack/resolve" actions, it lacks the flexibility to customize the actual alert content or the wording of messages sent to channels. Similarly, the API often feels restricted when trying to build more complex, automated workflows or custom internal tooling. I’d like to see more "hooks" for customization so the integrations can better fit our specific team processes rather than forcing us into a standardized format. Review collected by and hosted on G2.com.

I love that pager duty has several different audible alerts, some of them are hilarious. Since picking up pager duty, I've been able to respond to incident and engage teams more efficiently. Review collected by and hosted on G2.com.

The only thing that I don't like about Pager Duty is that once I resolve an incident I can not re open the same incident if the issue recurs I have to start a new incident which sometimes can cause confusion with stakeholders and users. Review collected by and hosted on G2.com.

PagerDuty ensures critical issues are notified to the right person via multiple channels (mobile app, SMS, email) and enables well-defined on-call rotations and escalation policies

integration with tools like Slack, Zoom, monitoring systems (e.g., Prometheus) and usage of webhooks to build automated incident workflows

can manage multiple teams, services, and global operations

the mobile app and remote acknowledgement/resolution functionality are called out as strong points Review collected by and hosted on G2.com.

- maybe new AI/automated workflows or automatic post-mortem functionality

- pricing is high relative to perceived value, especially for smaller orgs Review collected by and hosted on G2.com.