PagerDuty Operations Cloud

What do you like best about the product?

What I like best about PagerDuty is how it streamlines incident response and ensures the right people are notified immediately when critical issues occur. The alerting and escalation policies are highly customizable, making it easy to manage on-call rotations without worrying that important incidents will be missed.

What do you dislike about the product?

While PagerDuty is a powerful platform, some of its more advanced features come with a learning curve, especially when configuring complex escalation policies, event orchestration, and automation workflows. Initial setup can take time for larger organizations with multiple teams and integrations.

What problems is the product solving and how is that benefiting you?

PagerDuty helps us solve the challenge of responding quickly to critical incidents by ensuring alerts reach the right people at the right time. Instead of relying on manual notifications or monitoring dashboards, incidents are automatically routed through predefined escalation policies, reducing the risk of missed alerts and delayed responses.

I have used PagerDuty Operations Cloud for two years, so I have over two years of experience with it.

My main duties in PagerDuty Operations Cloud are incident routing, escalation policies, on-call management, incident response coordination, and integrations.

For incident routing, I connected AWS CloudWatch alarms to PagerDuty using the Event API. When our EC2 CPU crosses 85%, CloudWatch pushes the alert to PagerDuty, which then routes it to the backend services team. I also used event rules to auto-tag alerts and suppress duplicates. Another use case is on-call management. I used PagerDuty's mobile app to acknowledge alerts during off hours. For example, on weekends, such as Sunday morning, when there is an incident I acknowledged a high-priority alert from my phone and joined the Slack room directly from the PagerDuty incident link. This is helpful for those who are on call during off shifts. Regarding integrations, since we use many integrations on PagerDuty, we integrated PagerDuty with Slack so incidents automatically created a dedicated channel. I also connected it to Jira so incidents could generate tickets for follow-up actions, and also to ServiceNow as well.

PagerDuty Operations Cloud excels at routing alerts, managing on-call schedules, coordinating incidents, and automating remediation. These features make it helpful for the on-call team and the people who are working with PagerDuty Operations Cloud.

The feature I use the most is incident routing. We use incident routing more than anything else because it is the main foundation of PagerDuty Operations Cloud. If routing is incorrect, nothing else is going to work, no escalations, no on-call, and no automation at all. I use it the most because it is the first step in every incident; it ensures that alerts from different cloud platforms or any other third-party providers such as AWS, Azure, and other platforms including Datadog reach the right service. It prevents misrouted alerts and missed incidents and it directly impacts the MTTA, because responders get the alert instantly. Every other PagerDuty Operations Cloud feature depends on routing being accurate. I use incident routing daily in this way. This is the main foundation of PagerDuty Operations Cloud, to work with it and to make it a very easy platform for us to work with.

PagerDuty Operations Cloud excels at routing alerts, managing on-call schedules, coordinating incidents, and automating remediation. It ensures critical alerts reach the right teams instantly, reducing the MTTA and MTTR. It strengthened the on-call process with dependable escalations and real-time incident coordination, preventing missed alerts and speeding up resolution tasks. Automation and noise reduction features help cut down repetitive manual work and alert fatigue, allowing engineers to focus on real issues.

PagerDuty Operations Cloud significantly reduced alert noise and improved MTTA. Our acknowledgement time dropped almost by half, and MTTR improved by around 15–20% due to improved automation and routing.

The alert noise dropped by 20–25% after tuning event rules. After implementing PagerDuty Operations Cloud, we saw a 20–25% reduction in alert noise and a noticeable improvement in MTTA. Our acknowledgement time dropped by almost half and the MTTR improved by around 15–20%. MTTR improved by 15–20% due to major incident automation and better routing, which also reduced unnecessary on-call interruptions. It made a good impact on our current schedules and in my current organization.

PagerDuty Operations Cloud's alert reduction features helped lower operational cost by cutting unnecessary alerts and reducing on-call interruptions by grouping and suppressing noisy alerts. The team spent less time triaging low-value incidents, which directly reduced overtime and burnout. The biggest impact for us was fewer false alarms, meaning engineers could focus on real issues instead of constant alert fatigue.

PagerDuty Operations Cloud could improve its noise reduction by making deduplication and suppression more automated instead of manually tuned, and the service dependency graph could be more intuitive with cleaner visuals and easier-to-understand root cause tracing during major incidents. Automation could go further with smarter runbook triggers and AI-driven suggestions to help find root causes, which could save a lot of time for engineers who are struggling to understand what is actually happening. These AI capabilities could lower the time by maybe 50–60%. Analytics and reporting could be more flexible, allowing custom dashboards and filters and team-level MTTA and MTTR breakdowns, so that it is segregated based on teams and it is much easier to have custom dashboards for the teams to understand more.

Alert storms were a recurring frustration for the on-call team, and escalation overrides and service dependency graphs can get a bit confusing in larger environments. More customizable analytics and smarter automation would make the platform even easier, more flexible and more powerful for the team to understand.

PagerDuty Operations Cloud could improve its analytics flexibility with customized dashboards and AI capabilities to be more trained and more reliable. Service dependency mapping can also feel cluttered in big environments, making it harder to trace upstream and downstream impacts during bigger incidents.

We implemented PagerDuty Operations Cloud's AI to help with alert grouping and early incident insights, but accuracy was not consistent enough to rely on during critical events. It occasionally grouped unrelated alerts or missed correlations, which limited the operational efficiency gains we expected. The on-call team still depended heavily on manual triage because AI suggestions were not always aligned with the real root cause. Overall, AI added some value but it has not yet reached the reliability needed to significantly improve the incident response efficiency. It needs more training or more work.

PagerDuty Operations Cloud is stable in day-to-day use with no major outages or reliability issues affecting our on-call workflows. Alert delivery, incident routing and escalation chains have been consistently working without delays or missed notifications. Its cloud-native architecture also means updates and patches roll out smoothly without impacting uptime. Overall, the stability has been one of the strongest features for our team.

PagerDuty Operations Cloud scales well for growing teams. Adding services, integrations and new on-call groups does not impact performance. Its native cloud architecture handles higher alert volumes smoothly, especially when paired with strong incident routing. We have seen it manage increased workloads without slowing down or causing notification delays. On the whole, scalability has been reliable even as our environment and service footprint has expanded.

The customer support has been responsive and generally helpful when we have raised any issue. They provided clear troubleshooting steps and follow-ups. Resolution speed can vary depending on the severity of the issue, but support has been good and reliable for day-to-day operational needs.

Before PagerDuty Operations Cloud, we used basic native alerting tools such as AWS CloudWatch since AWS is our primary cloud platform. We switched because those tools lacked valuable incident routing and consistent on-call escalation workflows. PagerDuty Operations Cloud offered stronger coordination, better noise reduction, and more mature incident response features. The move was mainly driven by the need for a unified and dependable on-call and incident management platform.

We have actually seen a moderate return on investment mainly through reduced alert noise and more efficient incident routing. Alert storms dropped by roughly 20–25%, saving the team several hours per week that used to be spent on low-value triage. We estimate a small cost reduction from fewer overtime hours and less on-call fatigue, though not enough to reduce headcount. Overall, the return on investment is positive but incremental — more time saved than money saved.

PagerDuty Operations Cloud's pricing felt reasonable but it definitely is not the cheapest option. The value comes more from reliability than cost savings. Setup costs were minimal since it is a SaaS platform and onboarding did not require any infrastructure or hidden implementation costs or fees. Licensing is straightforward but scaling seats for larger teams can get expensive, especially when adding advanced features. Overall the experience was smooth but the price point could be more flexible for growing teams. Our team is small now but in the future it might become bigger.

Before adopting PagerDuty Operations Cloud, we evaluated options such as Opsgenie and Splunk On-Call for incident management. We also looked at other native cloud tools such as AWS CloudWatch, but they lacked the escalation workflows. Opsgenie had good features but did not match PagerDuty Operations Cloud's reliability and integrations for bigger teams. Overall, PagerDuty Operations Cloud offered stronger coordination and more consistent on-call performance which made us choose it.

Escalation policies are a very helpful feature for managing the team, such as multi-step escalation logic which is extremely dependable and prevents missed alerts, and also the automation runbook. I rely on incident routing daily because it ensures the alerts reach the right team. The other features, such as integrations, are really good to integrate PagerDuty Operations Cloud with different platforms, such as Jira and ServiceNow platforms to automatically open an incident. These are really helpful top features.

I would give PagerDuty Operations Cloud eight out of ten, considering all the features I have been using and also the improvements I have suggested. I chose eight out of ten because PagerDuty Operations Cloud is generally strong in the areas that matter the most, especially incident routing and escalation management which are extremely reliable and directly reduce MTTA and MTTR. It stands out for dependable on-call orchestration and smooth incident response coordination, especially with Slack and Jira integrations. But it does not reach a ten because noise reduction still needs more automation, analytics lack deeper customization such as custom dashboards to filter among the teams, and the service dependency graph gets cluttered in large environments. With smarter automation and improved visualization of the analytics, it could easily move closer to a perfect ten.

Public Cloud

Amazon Web Services (AWS)

What do you like best about the product?

Not much really

What do you dislike about the product?

I don't like PagerDuty that much. The billing is misleading and expensive. The UI makes it seem like the seats are auto-allocated and you can't decrease the number easily. But it turns out they keep charging you for a high number of seats, and you need to contact human support to reduce the seats, which feels like a scam. Plus, it's hard to find things, and everything feels old.

What problems is the product solving and how is that benefiting you?

I use PagerDuty for alerting on production errors, but I find the billing misleading and expensive. The UI is confusing, making it look like seats are auto-allocated, requiring human support to reduce them.

What do you like best about the product?

I like PagerDuty's reliable alerting, which ensures that critical issues are escalated to the right team quickly. The on-call schedules are easy to manage, and the fast incident escalation greatly helps reduce response times and improve team coordination. I also appreciate its seamless integration with other tools and how the mobile app makes it easy to respond to incidents from anywhere.

What do you dislike about the product?

I find the initial setup and configuration complex, and I think the pricing is high for small teams. I would also welcome more customizable reporting and a simpler interface for managing advanced configurations.

What problems is the product solving and how is that benefiting you?

I use PagerDuty for on-call alerting, incident management, and ensuring critical issues are escalated to the right team quickly. It helps us respond to critical incidents faster by automating alerts, reducing missed notifications, and streamlining incident coordination.

What do you like best about the product?

The best about PagerDuty is its realtime alerting and incident mechanisms. The great thing is its automated incident reponse workbook and its automation mechanisms

What do you dislike about the product?

If the configuration is not done properly then we may end up in getting false positive or true negative alerts and that will cause confusion. The pagerduty customizations are very limited

What problems is the product solving and how is that benefiting you?

The problem that PagerDuty solving is realtime incidenting and alert creation. PagerDuty is completely scalable. Its reporting and analytical capabilities are really helpful in tracking the metrics accurately

What do you like best about the product?

What I like best about PagerDuty is its ability to quickly notify the right people during incidents and help coordinate responses efficiently. The alerting system is reliable, and the escalation policies ensure that critical issues don't get missed. As someone involved in application support, I find the mobile app especially useful because it allows me to acknowledge and track incidents even when I'm away from my desk. The integration with monitoring and ticketing tools also helps streamline incident management and reduces response times. Also it does provide competetive pricing as per market requirements. It does come with great support where users can get the support on priority, and user interface is so interactable for easy understandings.

What do you dislike about the product?

One thing I dislike about PagerDuty is that the initial setup and configuration of escalation policies, schedules, and integrations can be a bit complex, especially for new users. The platform also has many features, which can make the interface feel overwhelming at first. Additionally, frequent alerts during high-volume incidents can sometimes contribute to alert fatigue if the notification rules are not properly tuned.

What problems is the product solving and how is that benefiting you?

PagerDuty helps us manage production incidents more effectively by ensuring that alerts are routed to the correct support teams without delay. Before using a dedicated incident management platform, there was a higher risk of missing critical alerts or delays in escalation. With PagerDuty, incidents are tracked, escalated automatically when needed, and resolved faster through better team coordination. This has improved our response times, reduced downtime, and helped us meet SLA commitments more consistently, which ultimately leads to a better experience for both internal teams and end users.

What do you like best about the product?

PagerDuty makes incident management much more efficient by sending instant alerts to the right team members. I like its reliable notification system, escalation policies, and on-call scheduling, which help ensure critical issues are addressed quickly. The integration with monitoring tools and collaboration platforms is smooth, and the mobile app allows me to respond to incidents even when I’m away from my desk. Overall, it helps reduce downtime and improves operational efficiency.

What do you dislike about the product?

If alrts are not configured properly engineers can receive multiple notifications making it harder to to identify critical issue alert tuning is required

What problems is the product solving and how is that benefiting you?

Help reduce downtime and respond it incidents faster it ensures right engineer is notified immediately when the issue occurs through automated alerts.

What do you like best about the product?

I use PagerDuty to manage incidents and on-call alerts for our team. I like how reliable the alerting system is; notifications are fast, ensuring the right person gets notified immediately, which reduces response time and helps us resolve incidents quickly. The on-call scheduling is easy to set up and manage, making it clear who is responsible at any given moment and avoiding confusion. PagerDuty works well with tools like Slack and Jira, which makes the incident response process much smoother. These integrations save us time since we don't have to switch between different applications. Alerts are shared in Slack, so the team can start discussions immediately, and if an issue needs tracking, we can create or update a Jira ticket, keeping all communication and tracking in one place. Overall, PagerDuty fits well with the tools our team already uses, adding significant value to our workflow.

What do you dislike about the product?

There are a few things that could be improved. The initial setup can take some time, especially if you're configuring complex alert rules and integrations. Some advanced features also have a learning curve for new users. The pricing can be a bit expensive for smaller teams, and it would be nice if more features were available in the lower-tier plans. The user interface could also be improved as some settings are spread across different sections, making it difficult to find what you're looking for, especially if you're a new user. It would also be helpful if the reporting and dashboards were more customizable without needing extra setup.

What problems is the product solving and how is that benefiting you?

PagerDuty helps us manage incidents effectively, ensuring quick alerts and reducing response time. It integrates with Slack and Jira, centralizing communication and incident tracking. On-call scheduling eliminates confusion about responsibilities.

What do you like best about the product?

I use PagerDuty in my day-to-day incident handling work. I appreciate how it brings cross-team engagements without any direct contact with the stakeholders of an incident. The monthly or weekly metrics on the number of incidents are great, and I find the initial setup to be easy.

What do you dislike about the product?

I find the searching space for an incident number not that visibly great on PagerDuty. It's a bit of a challenge to locate the search space on the green and white colored page.

What problems is the product solving and how is that benefiting you?

PagerDuty facilitates cross-team engagement without direct stakeholder contact and provides insightful incident metrics.