PagerDuty Operations Cloud Reviews

We are currently using PagerDuty Operations Cloud for incident management, escalations, on-call, and the status page, which represents our main product utilization.

What I like the most about it is that it has so many integrations like Azure integrations, AWS integrations, and Prometheus and Grafana integration for the alerting system, which makes it more convenient for us. We are using all kinds of tools like Grafana and others, which are easy to access and integrate with PagerDuty Operations Cloud. Our infrastructure is going to be more secured whenever incidents get triggered, and with the help of PagerDuty Operations Cloud, we are able to get incidents triggered automatically after alerts are triggered.

Currently, there is one tool called Rootly. I think they are new to the industry and we are also using that for one of our other clients. It's somewhat similar, but I think they have the potential to compete with PagerDuty Operations Cloud in the future as well.

As of now, we are not using any generative AI features in PagerDuty Operations Cloud. We are currently using it for on-call and other things.

What I like the most about it is that it has so many integrations like Azure integrations, AWS integrations, and Prometheus and Grafana integration for the alerting system, which makes it more convenient for us. We are using all kinds of tools like Grafana and others, which are easy to access and integrate with PagerDuty Operations Cloud. Our infrastructure is going to be more secured whenever incidents get triggered, and with the help of PagerDuty Operations Cloud, we are able to get incidents triggered automatically after alerts are triggered.

The benefits in terms of on-call are that we are getting maximum utilization of it. Previously, we were not having any alerting system for our client, and after implementing PagerDuty Operations Cloud, we started finding out the root cause and made other things easier compared to earlier. With the help of PagerDuty Operations Cloud, we are able to fix most of the issues and reduce repetitive issues in our infrastructure.

There is nothing I dislike about PagerDuty Operations Cloud, but perhaps it's due to the networks or the medium which it is taking. Usually, what happens is that if an incident gets triggered, suppose if it triggers in five to ten seconds, but sometimes, maybe due to latency or other factors, the call gets triggered after two or three minutes. That is quite understandable, but some kind of production issues need to be addressed at the earliest critical issues. So that latency needs to be reduced from PagerDuty Operations Cloud. I think they need to work on that. Apart from that, most of the things they are doing well, and we are not facing any such kind of issues. Everything is good.

Except for the frequency of the call, we don't see any lagging, crashing, or downtime. In rare cases, we hear some noises in the call, which is rare but not frequent. Apart from that, the triggering latency is a bit slow, but not every time.

We have been currently using PagerDuty Operations Cloud for more than two years.

Except for the frequency of the call, we don't see any lagging, crashing, or downtime. In rare cases, we hear some noises in the call, which is rare but not frequent. Apart from that, the triggering latency is a bit slow, but not every time.

Regarding scalability, I don't think there are any issues; it is going well.

We have very good support with PagerDuty Operations Cloud.

In few cases, not frequently, we have had to contact the technical support for clarification regarding the integration or for creating escalation things. Initially, we reached out to the technical support, but now we are well-versed with the tool. The community is good, and I think we are able to get solutions within the community itself.

For the support of PagerDuty Operations Cloud, I would give them a score of nine to ten.

Currently, there is one tool called Rootly. I think they are new to the industry and we are also using that for one of our other clients. It is somewhat similar, but I think they have the potential to compete with PagerDuty Operations Cloud in the future as well.

I don't think the deployment for PagerDuty Operations Cloud is difficult to handle. It is easy to handle, and the best thing is they have a very good support team that we can reach out to at any time.

The pricing for PagerDuty Operations Cloud is a bit expensive, especially for startups like us, compared to the other platform which I mentioned, which is Rootly. Rootly is not based on a per-user model. In PagerDuty Operations Cloud, it is going to cost fifty dollars per user for admins or other roles, whereas in the other platform there is no such kind of thing; it is based on a pay-as-you-go model. I think that is one of the drawbacks for PagerDuty Operations Cloud regarding billing and other aspects. Apart from that, the plans and other things for incident creations and the triggering of calls are quite good.

Currently, there is one tool called Rootly. I think they are new to the industry and we are also using that for one of our other clients. It is somewhat similar, but I think they have the potential to compete with PagerDuty Operations Cloud in the future as well.

The major part of PagerDuty Operations Cloud is for communication and pinging people and engaging them and pulling them into the call.

The most valuable thing I appreciate about PagerDuty Operations Cloud is the escalation process, where it automatically escalates incidents. It features a level one, level two, level three escalation process. When I engage or page someone at level one and start working on priority one or priority zero calls, and I am busy with those tasks, it automatically escalates to the next person in the chain of command, the second higher authority. There are many automation features in PagerDuty Operations Cloud.

If I complete one form, it automatically communicates with people and automatically scribes the incident in my ServiceNow incident. It automatically performs many tasks simultaneously, including sending Outlook emails. These automations are very important and well-known features in PagerDuty Operations Cloud, and they are the main reasons I value this product.

Infrastructure autonomous agents are installed in important servers and important devices in the infrastructure, and these are required components.

I do not have anything that I dislike about PagerDuty Operations Cloud. Sometimes it hangs and occasionally I am unable to open PagerDuty Operations Cloud, which occurs due to an outage or similar issues. Other than that, I do not have any other issues with PagerDuty Operations Cloud.

PagerDuty Operations Cloud developer team is working on enhancements. From my understanding, it is learning quickly and helping me when I require suggestions. PagerDuty Operations Cloud AI provides a combined benefit for my work.

I have been using PagerDuty Operations Cloud for six years.

PagerDuty Operations Cloud automatically learns based on the infrastructure. If I am in a commodity scenario, it learns in that specific way for that company. If I am in e-commerce, it learns in a different way for that industry. If I am in a hospital infrastructure scenario, it learns hospital-specific things and performs accordingly. This is an additional level of comfort for a PagerDuty Operations Cloud user, giving me extra convenience and suggesting many things immediately during priority calls.

For the stability of PagerDuty Operations Cloud, I rate it at 9.8.

Scalability for PagerDuty Operations Cloud is excellent, and I rate it at 9.9. I can scale it as and when required, however much I need. Because we do not place much load on PagerDuty Operations Cloud, I can scale as much as needed.

I have created tickets with PagerDuty Operations Cloud support. In those scenarios, I received good responses from PagerDuty Operations Cloud, and they provide informative assistance when required. I update that information into my ServiceNow ticket. I have received good technical support from PagerDuty Operations Cloud, and I do not have any negative comments regarding their support quality.

Initial deployment of PagerDuty Operations Cloud is easy and not difficult. It guides me through next steps and what to do and what not to do and where it should install and where it should not. It gathers the necessary information during the setup process.

I used Slack as an alternative to PagerDuty Operations Cloud. I have used Slack, Microsoft Teams, Outlook, and sometimes Zoom instead of paging PagerDuty Operations Cloud. I call people directly using Zoom in those situations. These are the alternative communication tools I have used instead of PagerDuty Operations Cloud when I face problems opening it, as sometimes it does not open and some links do not function properly.

Maintenance is not a concern because I am installing PagerDuty Operations Cloud into the supportive infrastructure and then connecting that to the production infrastructure, so it does not require any maintenance. I rate this product a 9 overall.

The main use case for using PagerDuty Operations Cloud is that we get paged as and when required for all the issues and incidents which are happening, rather than requiring us to keep track of all of them. We are in the exploring phase for using AI around PagerDuty, but that is still in exploration and we haven't started with that.

When there is an incident, we get paged for an alert. We have escalation policies set up that are being followed, and if someone is not acknowledging the page or if someone is not available, then accordingly it will go to the next level of escalation. This ensures that none of the alerts are missed.

PagerDuty Operations Cloud has multiple integrations. In our case, we use the Slack integration the most. The alert triggers from our SignalFx stack, goes to PagerDuty, follows the escalation policy, and reaches the user. Along with that, it is also sent to the Slack channels so that whatever triaging happens for that alert or incident happens over Slack in that particular thread where the alert is triggered from PagerDuty.

PagerDuty Operations Cloud is very easy to use and user-friendly.

Regarding the features that PagerDuty Operations Cloud offers, I have explored the automation area and it has a good amount of integrations. For example, the event intelligence and the noise reduction are areas where PagerDuty is really powerful. It reduces and cleans up alerts by doing alert de-duplication and alert grouping. It has also recently got machine learning capabilities, which would surely be helpful. We also have automations and runbooks in place which can help to do auto-remediation of issues or trigger scripts as per the runbooks. We haven't been using all of those things, but I know that these things are present. The incident response on-call management is very easy to use with PagerDuty. There are flexible on-call schedules, escalation policies, and the ability to set up overrides easily. There are multiple channels by which you can send alerts including SMS, calls, and notification pushes.

PagerDuty Operations Cloud also has war room features. Many emerging tools provide this as well, but since PagerDuty is a pretty established company, it has a very mature model with all of these features. The analytics and reporting are also decent.

PagerDuty Operations Cloud has improved our incident management process by ensuring that the right set of people are notified within time. The best part is that it has automated on-call schedules and escalation policies, so you don't have to set them again and again for every week or every month. Features including alert grouping, alert de-duplication, and good analytics and reporting are very helpful during incident management and also for post-incident activities.

The analytics and reporting have some scope for improvement. First, it should have more granular capabilities and we should be able to query it in a more granular way. There should also be more advanced trend analysis or cross-team operational insights available. That would be helpful. Licensing is also a bit expensive, so there should be some cost optimization for large deployments to take care of licensing cost optimization. Since we are in the AI era, I know PagerDuty has been investing in a lot of AI capabilities, but there should be good enhancements which we are looking forward to, such as automated root cause analysis or doing historical pattern matching. There could also be recommendations around runbook automation.

I have been using PagerDuty since the last one and a half years at Splunk, and before that I was also an active user of PagerDuty in my last organization.

PagerDuty Operations Cloud is stable.

PagerDuty Operations Cloud is pretty scalable. I never had any issue where a large number of alerts impacted PagerDuty.

The support is decent.

Previously, we were using OpsGenie, but that was quite a long time ago. PagerDuty Operations Cloud already has all the things which OpsGenie had, as per my knowledge.

The costing took away two points from my overall rating. There are still some good amount of areas of improvement which took away the last one point, resulting in a rating of seven out of ten.

I am not in the position to select any tool. I am not the one who selected or chose PagerDuty or evaluated any tools before that. We are just end users.

The return on investment is nine out of ten.

We are still in the phase of doing that evaluation and it is not yet completed. However, it is pretty helpful because PagerDuty itself has a good amount of data which can be used with AI to make the best use of it. I am still in the experimenting phase, but the AI functionality of PagerDuty would definitely be a good way to analyze the ongoing issues and how issues are handled right now, tracking the MTTR and MTTDI, and finding spots where there are a lot of areas of improvements which are needed.

PagerDuty Operations Cloud already has a lot of integrations available, which is pretty good. The user experience is swift and smooth, which is a very good thing about PagerDuty Operations Cloud that I appreciate. I am not very aware of the governance and security aspects, but it has SSO as well, which is pretty good. Many organizations would be happy to adopt it, though I am not very aware of these features. The AI capabilities are not very reliable or accurate at the moment, but it is in the development phase and should improve over time.

I don't have the exact metrics available, but there is a significant amount of improvement which we can see after onboarding to PagerDuty Operations Cloud. Normally, before PagerDuty Operations Cloud, I can compare with my previous to previous organization because in that company we didn't have PagerDuty Operations Cloud. There were quite a good amount of alerts which were getting missed. With PagerDuty Operations Cloud, there is a good layer of notifications and notification policies that you have. Even if you miss any page, you will get a push notification on your mobile. If you miss that, you will get a call on your mobile, which is pretty good.

The overall pricing, setup cost, and licensing are pretty expensive. The PagerDuty Operations Cloud licensing is a bit confusing because it is primarily based on users, not on the number of alerts or incidents which are triggered. If it is a small organization, it is good, but if it is a large organization, it is difficult because many people would need to use PagerDuty Operations Cloud. At the same time, to make it more efficient or to get the best out of it, we need to have an end-to-end setup on PagerDuty Operations Cloud, which does take time. There should be some flexible licensing options.

PagerDuty Operations Cloud is a pretty mature product. If you are a mid-scale organization who is trying to get the best out of PagerDuty Operations Cloud, I would recommend going for it. My overall rating for this product is seven out of ten.

I primarily use PagerDuty Operations Cloud for on-call rotations, managing and creating schedules for on-call rotations, and incident management. Pages are triggered whenever an integrated tool creates incidents or tickets, and notifications are received through mobile SMS, phone calls, and integrated emails from PagerDuty Operations Cloud.

The learning curve is noticeable, and integration with other tools varies in ease. PagerDuty Operations Cloud is an evolved product compared to Opsgenie, but Opsgenie can better integrate with Jira and Jira Service Management. For third-party and open-source applications, PagerDuty Operations Cloud is superior. PagerDuty Operations Cloud offers stronger incident management, better escalation policies, and greater reliability as an evolved product with fewer bugs and improved reporting.

Notifications are received very easily and quickly whenever a page or incident is triggered in PagerDuty Operations Cloud. Notifications are not limited to a single medium. If a person is unavailable on one medium or notifications are suppressed, repeated notifications arrive one after another. For example, if a person does not respond to email, a text message will follow, then a phone call, and if still unresponded, escalation occurs to another level. This is beneficial from a management perspective, but can feel overwhelming when handling on-call duties, especially during stressful periods.

Incident responses in PagerDuty Operations Cloud are not delayed, with instant notifications enabling quick reactions. Escalation policies ensure that if one person is unavailable, the alert escalates to the next level and beyond, preventing missed incidents. PagerDuty Operations Cloud is very useful for root cause analysis and audits, documenting each action including when a person viewed information on the app, received or declined calls, accepted or acknowledged alerts, the time before acting on incidents, and when incidents were resolved or closed. The mobile interface is effective, and managing escalation policies, schedules, and related items is easier compared to other tools.

PagerDuty Operations Cloud has been highly beneficial, preventing numerous outages through prompt response and incident alerting capabilities, demonstrating significant ROI.

Recent changes have been introduced, but the organization has not adopted them because artificial intelligence features are expensive and PagerDuty Operations Cloud itself is costly, limiting adoption across all organizations. Opsgenie was also used but found to be inferior as PagerDuty Operations Cloud is a more mature tool for incident response handling. PagerDuty Operations Cloud has easy integrations with numerous monitoring and alerting tools including ELK stack, Prometheus stack, Slack, and Jira.

While artificial intelligence has been introduced to PagerDuty Operations Cloud, it has not been tried due to operational blockers. There should be artificial intelligence that filters duplicate alerts or performs sentiment analysis. For example, when a person receives too many alerts, they can become frustrated. If there are ten alerts where seven or eight are false or low priority but a person still receives repeated pages, the remaining two alerts have a higher chance of being missed or not receiving adequate attention. This occurs in live cases and has been observed. Setup and integration remain easier compared to other applications like Opsgenie, though a learning curve still exists for management and new users, suggesting a simpler approach to setup and monitoring integration would be beneficial.

Pricing is expensive. Too many alerts are received, and the organization largely depends on optimizing alerts at the application level rather than the alerting level. A mechanism on the alerting side to filter or optimize alerts would be valuable. PagerDuty Operations Cloud is somewhat complex in comparison to Opsgenie, which has a simpler interface.

I have worked continuously with PagerDuty Operations Cloudfor about three and a half years.

PagerDuty Operations Cloud is stable.

PagerDuty Operations Cloud is scalable. Any number of alerts can be deployed and grouped. Alert grouping is quite effective. Multiple team members can be onboarded, and escalation and scheduling policies can be created in an efficient manner.

Customer service could be easier to reach and quicker in responding. There is some latency in receiving responses.

PagerDuty Operations Cloud has been highly beneficial, preventing numerous outages through prompt response and incident alerting capabilities, demonstrating significant ROI.

Work occurred with management on creating escalation policies and automated schedules using the web application of PagerDuty Operations Cloud, along with integrations to different applications and mediums including SMS, email, Slack, Jira, and Microsoft Teams.

PagerDuty Operations Cloud was deployed in the cloud as a Software as a Service offering.

Tech support would be rated at 7.5 out of 10.

PagerDuty Operations Cloud is a more evolved product and more stable than alternatives. Organizations with sufficient financial resources and without budget limitations can opt for PagerDuty Operations Cloud compared to other products. The overall review rating for PagerDuty Operations Cloud is 8 out of 10.

My main use case for PagerDuty Operations Cloud is mostly for monitoring and alerting, and we are also using it for Jira and Slack integrations.

I mostly use PagerDuty Operations Cloud for monitoring and alerting through Jira and Slack integrations, where we create a ticket and if we want to close the ticket then we use the PagerDuty Operations Cloud dashboard itself instead of going through the Jira dashboard and closing it manually, so integrations helped a lot. Even with the Slack integration, instead of closing directly on PagerDuty Operations Cloud, we can close it on the Slack message itself.

I think the API usage for PagerDuty Operations Cloud is also helpful.

The best features PagerDuty Operations Cloud offers include all the required things needed, and I think I am good as it has the people and the team management, and everything looks good.

Regarding team management in PagerDuty Operations Cloud, I appreciate how it shows which people are API, people who can manage API, and who can manage the entire systems, and that's good actually.

PagerDuty Operations Cloud has positively impacted my organization as I think the mean time to resolve has reduced significantly.

The solution's alert reduction feature has had a positive impact on preventing costly incidents in our organization as we have reached our SLAs due to that, by reducing alert noise.

I think PagerDuty Operations Cloud can be improved cost-wise as it is a bit high when compared with Opsgenie services that are offered by Jira, so I think if you can manage that part it will be good.

I would like to add that everyone is integrating AI into their tools, and I am unsure whether PagerDuty Operations Cloud has that at the moment besides the cost.

I choose nine out of ten because I think there should be some edge cases including integration with AI. Every tool is evolving, so I think PagerDuty Operations Cloud still needs some more advanced features to compete with other services.

I do not have much idea about PagerDuty Operations Cloud's AI capabilities when it comes to governance and security, but we need to set guardrails for it on its capabilities.

Regarding PagerDuty Operations Cloud's AI capabilities, I think it is mostly reliable, as far as I know, when it comes to its accuracy and reliability of output.

I have not implemented AI and automation through PagerDuty Operations Cloud for incident response, and I am not aware of how it has changed our operational efficiency because it was not really needed during that time.

I am not aware of any ways PagerDuty Operations Cloud's AI functionality has improved my team's ability to focus on core tasks rather than routine issues.

I would assess the effectiveness of PagerDuty Operations Cloud's generative AI in providing insights for decision-making as something that would be good if it can reach SLAs and eliminate false alarms.

It has been one year since I have been using PagerDuty Operations Cloud.

PagerDuty Operations Cloud is mostly stable at ninety-nine point nine percent.

I am unsure about PagerDuty Operations Cloud's scalability because that is based on cloud; it is not hosted.

I did not really need to reach out to customer support as everything worked normally, and we can get all the information through the documentation.

Without PagerDuty Operations Cloud, we used other tools including CloudWatch alerting, but that did not help to resolve the issue. However, with PagerDuty Operations Cloud, I think it pointed the exact root cause, including which service is failing, based on PagerDuty Operations Cloud scripting.

We previously used a different solution, CloudWatch alerting, but we had to use our own way of writing Lambdas, which did not alert on phones or based on timing, geographic location, and that is the reason why we had to switch to the enterprise-level PagerDuty Operations Cloud so we can create schedules and alert based on alert policies.

We do not purchase PagerDuty Operations Cloud through the AWS Marketplace as it is a separate licensing, not through AWS.

I have not seen a return on investment regarding employees or money saved, but mostly the client commitment that we have given has reached, and it is good.

My experience with pricing, setup cost, and licensing is that it is all managed by upper management, so they did not reveal the pricing or other details, but what I heard was that it is better to use Opsgenie after using PagerDuty Operations Cloud because of pricing and licensing.

Before choosing PagerDuty Operations Cloud, we evaluated other options including Jira's Opsgenie, but I think it does not have really matured the way PagerDuty Operations Cloud has.

My advice for others looking into using PagerDuty Operations Cloud is that nowadays there are many tools, but we need to make sure whether it matches our business requirements including integrations, whatever PagerDuty Operations Cloud integrates, and then go with PagerDuty Operations Cloud because it is easy to use. I gave this review a rating of nine out of ten.

My usual use cases with PagerDuty Operations Cloud involve handling incidents through a full flow. When there is an outage, an incident is created that can be either severity one or severity two. As the person on call that day, I receive a page from PagerDuty on the app and three calls on my cell phone. When I pick up the call, PagerDuty IVR asks me to acknowledge the incident. Once I acknowledge the incident from the call, I go to PagerDuty through the website, which is much easier to navigate than the mobile app. I then page other teams responsible for the incident, as well as the stakeholders and product owners.

PagerDuty is integrated with Microsoft Teams, so I open a Teams bridge call to resolve the issue and update all incident details in PagerDuty notes, which automatically integrates with ServiceNow incident and sends messages to stakeholders' phone numbers.

One time while hanging out in the mountains, there was no internet signal but there was cell reception. An incident happened while I was on call that day. Normally, without internet, I would not be able to know about it, but because of PagerDuty, I was paged three times on my cell phone as well as through text message. I managed to call another colleague from my work and told him to take care of the incident. This helped me avoid breaching the SLAs on incident acknowledgment and allowed me to access remote incidents without relying solely on the internet.

The features of PagerDuty Operations Cloud that I find most valuable involve being automatically paged whenever an incident is triggered. PagerDuty has group names embedded into it, and when we set up PagerDuty in our organization, we embedded the group name, allowing me to page other respondents without having to go separately into Microsoft Teams, add everybody's name, and then ping and call them. I can do this directly from PagerDuty itself.

The notes update feature allows me to put the details of the incident in the notes and click post, and it is integrated everywhere. Everything is centralized.

PagerDuty Operations Cloud has improved my team's ability to focus on core tasks rather than routine issues primarily due to its availability and reliability. We do not worry about whether PagerDuty will call us when an incident triggers, allowing us to focus on that incident. The notes update process ensures that everyone gets informed with just one update.

I think PagerDuty Operations Cloud could be improved by having two fields for incident updates. In my work, I handle incidents that have two fields: work notes visible only to developers working on the incident and additional comments visible to the client. When I update through PagerDuty, everything gets updated into the additional comments. There should be two fields, perhaps based on how it is integrated with ServiceNow.

I have not used PagerDuty's autonomous AI agents or generative AI, so I am not sure whether it is integrated.

I can evaluate the effectiveness of PagerDuty Operations Cloud in providing insights for decision-making, and I rate it around seven out of ten. PagerDuty Operations Cloud is really helpful. With generative AI integrated and a chatbot, I think it would bump the rating up to nine, but I have not used it yet, so I cannot say for certain.

I have been using PagerDuty Operations Cloud for around one and a half years.

Regarding the reliability and stability of this product, I find it really stable. Based on my personal experience in the mountains, I can vouch for it. My organization measures the acknowledgment rate by checking how many times a call rings and how quickly the responder acknowledges the incident. The acknowledgment rate is really good, around ninety to ninety-five percent.

I think the scalability of PagerDuty Operations Cloud is superb. It can handle many requests according to demand. As other members and teams are added to our organization, it has not impacted the latency, call failure, or anything else. The performance is really good.

I do not often communicate with the technical support of PagerDuty. The manuals are created by our team, so we use those.

I did not use a different solution for the same use case before PagerDuty Operations Cloud. PagerDuty Operations Cloud was the first solution I used.

I did not participate in the initial setup of PagerDuty Operations Cloud. When I joined the organization after one and a half years of use, it was already set up for me by the IT team.

I have not personally implemented automation through PagerDuty for incident response, but I think some of my colleagues may have done so.

I am not aware of the impact of PagerDuty's alert reduction feature on preventing costly incidents in our organization, as that metric is not shared with me.

I am not sure about the influence of PagerDuty Operations Cloud on revenue protection in terms of reducing alert fatigue and incident costs, as these are organizational-level decisions, and employees are not involved in those discussions.

Before PagerDuty Operations Cloud was chosen, I did not evaluate other options, as the decision was made by the board members.

My review rating for PagerDuty Operations Cloud is seven point five out of ten.

Public Cloud

Amazon Web Services (AWS)

My main use case for PagerDuty Operations Cloud is to handle all technical perspectives of incident management and real-time alerting. I primarily use PagerDuty Operations Cloud for the health tech environment, specifically in telemedicine platform and EHR-related applications, where it is required to ensure high availability.

PagerDuty Operations Cloud offers excellent features including the alert system and automated incident escalation capability, which is effective for routing issues to the right team through mobile notifications, SMS, or phone calls.

The real-time monitoring feature in PagerDuty Operations Cloud makes the biggest difference for my team, as it is quite helpful for on-call management and day-to-day operations.

PagerDuty Operations Cloud has positively impacted my organization by working effectively with most cloud service providers like AWS or Azure, improving visibility and reliability of incident responses.

I have seen a reduction in incident response time, with MTTR efficiently reduced by 30 to 40%, better SLA compliance, and improved operational visibility through incident analytics and reporting dashboards since implementing PagerDuty Operations Cloud.

The alert reduction feature in PagerDuty Operations Cloud has minimized downtime and improved incident response efficiency in my organization.

There are a couple of areas where PagerDuty Operations Cloud can be improved, such as enhancing Event Intelligence and alert grouping features and simplifying the initial configuration of escalation policies.

I have been using PagerDuty Operations Cloud for more than two years.

PagerDuty Operations Cloud is stable.

The scalability of PagerDuty Operations Cloud is quite good, as it works well with enterprise-level systems.

Customer support for PagerDuty Operations Cloud is quite effective.

Before implementing PagerDuty Operations Cloud, I relied on basic monitoring tools and email alerts for health tech monitoring, and I noticed a significant improvement after switching.

I have not reached ROI yet, but I am close, with a reduction in downtime and faster incident resolution.

I would say the pricing is quite mid-range, but the setup cost and licensing can sometimes be a little challenging.

Before choosing PagerDuty Operations Cloud, I evaluated basic monitoring tools and email alert systems but found that PagerDuty offered stronger integration and operational visibility.

I would advise others to clearly define their incident management strategy before implementing PagerDuty Operations Cloud. I would rate this solution a 7 out of 10.

Hybrid Cloud

Microsoft Azure

I appreciate how PagerDuty makes incident handling faster and more organized for teams. We use it to ensure the right people and teams get the right information about the right problems at the right time. The intuitive and user-friendly interface of PagerDuty logs incidents and helps me track issues encountered with software and apps on my workstation.

It requires very few details such as a date, time stamp, and a brief description of the issue to get started. Although the integration was a bit time-consuming.

Key features include resolving and tracking incidents in real time, 24/7 monitoring and scanning of issues, reliable alert escalation, and seamless on-call scheduling across teams.

I would like to see the configuration simplified, and the integration setup should be correct on the first attempt.

I have used PagerDuty for three years.

We previously used Zabbix. We needed a more robust and scalable alert tool that would manage how teams respond to alerts. PagerDuty helped us handle incidents better by assigning alerts to the right person, managing on-call schedules, and auto-escalating if no one responds.

It is a great tool for alerting the right team and assigning tasks to the right people so those problems can be solved in the correct time.

We considered Zoho Analytics and LogicMonitor as alternate solutions.

We've seen faster response times which helped reduce downtime. This saved revenue by avoiding long outages and improved team accountability during incidents.

My primary use case for PagerDuty Operations Cloud is for the on-call support that my team provides. We work in two phases: we build and architect things, and then we support them. Every week, two engineers from my team serve as on-call support engineers for any escalation tasks or emergencies that may happen with our production environment. We have monitoring and observability enabled for our services, applications, and servers. Whoever is the on-call engineer for that particular week follows an escalation matrix with five people: two primary and secondary on-call engineers, two primary and secondary management contacts, and the highest level, which is CVP. If something is not resolved by the primary engineer, it escalates to the secondary engineer, then to primary management, secondary management, and so on. We have a predefined roster that has been scheduled for approximately the next year, where each primary engineer is assigned a week. Every engineer is assigned a role as either a primary or secondary on-call engineer, and any escalations during that period are managed by PagerDuty Operations Cloud and communicated to the primary engineer, who then acknowledges it, resolves it, escalates it, or takes whatever action is needed.

The best features of PagerDuty Operations Cloud are that it is a fairly good tool for alerting. Here is how the process works: suppose there is an XYZ server in my environment hosting a production or development application, and a primary on-call engineer has been assigned for that particular week. We have set up monitoring and observability for that node so that if the node is not reachable, an alert is triggered and sends a notification to our integrated Slack channels with PagerDuty Operations Cloud. If the engineer is available, they can acknowledge the alert. If they fail to acknowledge it, the system calls them on their provided number. If that is also not acknowledged, it sends a text message. If those actions are not acknowledged, it sends an alert to the secondary engineer and calls them as well. This multi-channel approach makes it very difficult to miss an important alert or update. PagerDuty Operations Cloud handles this process perfectly, and we do not miss any alerts because of this system.

Regarding the stability of PagerDuty Operations Cloud, I cannot recall an incident where it was not available. I can say that it is 100 percent reliable for my needs.

PagerDuty Operations Cloud itself functions well, but our setup sometimes feels irritating. The calls come very early in the morning, and even after we acknowledge them, numerous calls from PagerDuty Operations Cloud pop up before we have fully woken up. We try to snooze them, but this is a result of how we have configured our alerting mechanisms rather than a PagerDuty Operations Cloud issue.

Another piece of feedback is that there should be more options for changing the automated voice that calls us. The automated voice could be better as it is not very interesting and feels outdated. I have not seen updates to it during the time I have been using PagerDuty Operations Cloud. I do not see many updates made to PagerDuty Operations Cloud overall. The UI is simple, but it should be refreshed periodically to keep up with current times. Everything needs a fresh appearance periodically.

I have been using PagerDuty Operations Cloud for the past four years.

PagerDuty Operations Cloud's scalability as a solution is fairly straightforward and has maintained its effectiveness. With new integrations being launched periodically, such as Slack and Datadog, the platform has blended itself well from an integration perspective. Whatever top-notch tools we are using as an enterprise solution, PagerDuty Operations Cloud has kept itself current and integrates nicely with all the tools we use these days. Even with upgrades we are making, such as adopting AI agents and using the latest AWS services like Bedrock and SageMaker, it is fairly easy to integrate with PagerDuty Operations Cloud. The platform also provides the option of changing rosters. PagerDuty Operations Cloud has a mobile application that I can use on my mobile phone, and it is fairly easy to use from mobile as well. I can change my rosters and reach out to my primary management and other contacts through the mobile app. It has kept up with recent times and continues to evolve.

I was not involved in the deployment of PagerDuty Operations Cloud because it was already in my organization when I joined. However, after using it for the past four years, I can say it does not need much complexity. The architecture is straightforward, as PagerDuty Operations Cloud is integrated with my Datadog and Slack systems. The integrations are easy, and it is now being integrated with AI agents as well. In the UI, I can see who is on the schedule. Although I was not involved in the deployment, I know it is fairly easy to use.

I would rate PagerDuty Operations Cloud around a nine out of ten. I deduct one point for the lack of updates to the UI, as the platform has not made many updates to its interface. Despite this, it does the job that it needs to do, and I would rate it a nine.

I am an end user of PagerDuty Operations Cloud in my organization, with a background in incident management. I primarily use it for managing on-call schedules, triggering and handling incidents, and monitoring alerts. It helps ensure timely responses, efficient escalation, and better coordination during incidents, making it a key tool for maintaining operational reliability.

PagerDuty Operations Cloud has improved our incident response by ensuring reliable alerting and faster escalation to the right teams. It has significantly reduced alert fatigue through better alert filtering and deduplication. The platform has also lowered our mean time to resolve (MTTR) with runbook automation and streamlined on-call management, leading to fewer disruptions and improved overall operational efficiency.

The features of PagerDuty Operations Cloud that I have found the most valuable and useful include alerting, which is very reliable with minimal delays, and the escalation policies and routing rules that are more flexible. Additionally, the on-call scheduling capabilities are great, and it integrates well with any cloud platforms such as AWS, GCP, or Azure, and observability tools such as DataDog and New Relic for logging and checking out logs.

I have noticed that PagerDuty Operations Cloud influences revenue protection by reducing alert fatigue and incident costs. AIOps has helped recently in reducing noise and alert duplications, and runbook automations aid in lowering the mean time to resolve by integrating triggers to Slack and updating runbooks.

I see PagerDuty Operations Cloud as a very good incident management and on-call platform, mostly used by large-scale organizations because it comes with premium pricing, but it is very reliable with alerting and on-call scheduling, triggering incidents, escalation policies, rules, and runbooks.

I think an area of PagerDuty Operations Cloud that could be improved is their premium pricing, as it compares unfavorably with competitors such as Atlassian's Opsgenie and ServiceNow, which offer bundle deals, plus DataDog now has incident management capabilities. Overall, the premium pricing makes it less accessible for small to medium businesses.

I think the pricing of PagerDuty Operations Cloud is a bit too high, and also, the UI can feel a bit curvy for new users; the learning curve might be a bit dense for them. The initial setup is straightforward, but the event orchestration could be complex, and the automation workflow definitely requires great expertise.

I have been using PagerDuty Operations Cloud for approximately four years.

I would rate the stability and reliability of PagerDuty Operations Cloud 9.5 out of 10. The platform is highly stable and dependable in production environments, especially for critical incident management workflows. We have experienced consistent alert delivery, reliable on-call scheduling, and minimal downtime or disruptions.

That said, no system is completely perfect, so I cannot say it is 100% flawless. However, overall it has proven to be very reliable for mission-critical operations, where even small delays or failures would have significant impact.

I would rate the scalability of PagerDuty Operations Cloud 8 out of 10. From a technical perspective, the platform scales very well and can support large, distributed teams with complex incident management needs. It handles high volumes of alerts, multiple services, and integrations across cloud platforms efficiently.

However, the main limitation to scalability is its premium pricing. As organizations grow and onboard more users or services, the cost increases significantly, which can be a challenge for small to mid-sized teams. So while it is technically highly scalable, cost can be a limiting factor for broader adoption.

I have had regular interactions with PagerDuty Operations Cloud’s technical support, and my overall experience has been positive. The support team is responsive and helpful in addressing queries.

For example, during a user audit, I requested specific data on active users and those who had not accepted invitations. The support team responded quickly and provided the required information without delays. Overall, the support experience has been efficient and reliable when assistance is needed.

I have only been using PagerDuty Operations Cloud; recently with my new organization, I am also using Fire Hydrant.

I was not directly involved in the initial setup of PagerDuty Operations Cloud, as it was handled by senior team members. However, from my observations, the setup process appears to be straightforward at a basic level for core features like alerting and on-call scheduling.

That said, advanced configurations such as event orchestration and automation can become complex. If rules are not configured properly, they may lead to alert storms or missed incidents. Additionally, runbook automation is not plug-and-play and typically requires scripting knowledge and careful setup to function effectively.

From an ROI perspective, I do not have direct visibility into financial metrics, so I cannot quantify exact cost savings. However, I have seen strong operational ROI from PagerDuty Operations Cloud.

It has improved incident response efficiency by reducing alert fatigue, ensuring faster escalation, and lowering mean time to resolve (MTTR) through runbook automation. These improvements have helped prevent prolonged outages and reduced the impact of incidents, which indirectly contributes to cost savings and better service reliability at an operational level.

I have some exposure to its autonomous AI agents, I have not extensively used its AIOps or generative AI capabilities. Despite that, the platform has had a strong positive impact on our operations.

By properly configuring alerting rules, we have been able to significantly reduce alert fatigue and shift focus toward more critical issues rather than routine noise. PagerDuty has also helped in reducing the number of duplicate alerts through intelligent pattern recognition.

Additionally, runbook automation has contributed to lowering our mean time to resolve (MTTR), enabling faster and more efficient incident handling. Overall, it has helped prevent costly incidents and improved operational efficiency across the team.

My review rating for PagerDuty Operations Cloud is nine point five out of ten.

Hybrid Cloud

Amazon Web Services (AWS)