PagerDuty Operations Cloud

PagerDuty Operations Cloud is part of our daily operational workflow. It sits between monitoring tools and response teams, ensuring alerts reach the right people without delay. We use it for on-call scheduling, incident escalations, and coordinating responses across teams. Having everything centralized has reduced alert fatigue and helped us respond to issues more consistently, especially during off-hours and high-priority incidents.

PagerDuty Operations Cloud offers intelligent alerting, on-call scheduling, automated escalations, and incident management as its best features. The platform makes it easy to ensure alerts reach the right person, and escalation policies prevent critical issues from being missed. We also rely heavily on its integration with monitoring and collaboration tools and its real-time visibility into operations. Together, these features help our team respond faster, stay organized during an incident, and reduce service disruptions for our customers.

While PagerDuty Operations Cloud is strong overall, there are a few areas for improvement. The initial setup and configuration can be complex, especially for teams managing multiple services, escalation policies, and integrations. Some reporting and analytics features could offer more customization without requiring additional configurations. The mobile app works well for alerting, but managing more advanced settings is generally easier from the web interface. It would also be helpful to have more out-of-the-box workflow templates and automation recommendations to simplify onboarding for new teams.

To make the daily workflow smoother, simplifying the user interface for certain administrative tasks would be a significant improvement. Sometimes, navigating the settings to adjust on-call schedules or escalation policies can take a few extra steps, particularly for large environments. More customizable dashboards and easier reporting for non-technical stakeholders, along with additional guided recommendations for alert tuning, could help teams get even more value from the platform. These are relatively minor points, but addressing them would make an already great tool even more user-friendly.

I did not give PagerDuty Operations Cloud a perfect rating because there is still room for improvement in areas such as reporting flexibility, dashboard customization, and simplifying certain administrative tasks. Overall, it is a mature and dependable platform that positively impacts our work.

As a cloud operation team, I was a user who set the alerts, and whatever important incidents or anomalies were detected that needed to be immediately taken care of were bifurcated through our APM  tools that we integrated with PagerDuty Operations Cloud . As a cloud operation team, we supported the platform for rotational shifts. My roles involved setting the person in the shift according to the shift roster, so whenever any incidents triggered, they would get the call. The primary use was supporting production operations and cloud activities.

Our multi-environment consists of AWS  infrastructure, Linux servers, Kubernetes  clusters, and customer-facing applications. PagerDuty Operations Cloud was mainly used for incident management and alerting. We integrated it with AppDynamics, Instana, and CloudWatch, where it would monitor the patterns and platform, and then PagerDuty Operations Cloud would generate the critical alerts that the appropriate support team who was working in that present shift would get notified of immediately. This platform really helped us manage production incidents beyond service outages, mostly high CPU utilization where we set alerts, application failures, pod issues in Kubernetes , and infrastructure-related alerts. We configured all kinds of alerts, which ensured that alerts were routed to the correct on-call person, helping us reduce response time in critical situations.

One of the best features I would mention about PagerDuty Operations Cloud is its on-call rotational scheduling support and escalation management practices. If an engineer did not acknowledge the alert within a defined time frame, the incident was automatically escalated to the next person, support team, or manager of that specific team. Another useful feature was its integration capability. We were able to integrate PagerDuty Operations Cloud with monitoring and observability tools that allow alerts to generate automatically whenever issues were detected in the environment within a fraction of time. We also had the mobile application that was very helpful because the engineer could receive calls, notifications, and acknowledge the incident and track the updates even when they were away from their laptop.

I also valued the centralized incident management dashboard that provides visibility into active incidents, response status, escalation history, and overall operational health. I used to get all the data accumulated there through the dashboard.

PagerDuty Operations Cloud helps us manage production incidents beyond service outages, mostly high CPU utilization where we set alerts, application failures, pod issues in Kubernetes, and infrastructure-related alerts.

My experience with PagerDuty Operations Cloud has been positive overall. One area where I believe improvement can be made is reporting and dashboard customization to make it more user-friendly. The operations team often requires different views compared to the management team. Having more flexibility in generating custom reports would be helpful. Another improvement could be providing more advanced AI-driven collaboration capabilities to reduce unnecessary noise alerts and help the team focus on the most critical issues. Apart from these areas, the platform is very reliable and effective for managing production incidents and on-call operations.

I have been using PagerDuty Operations Cloud for almost five to six years.

PagerDuty Operations Cloud has been stable and performing well wherever our incident management or alerting was configured for production support. Timely notifications and incident responses were critical. PagerDuty Operations Cloud delivers alerts immediately through multiple channels which we configured, including mobile on-call notifications, email, SMS, and phone calls. Since PagerDuty Operations Cloud was integrated with our monitoring and observability tools, it helped ensure that critical incidents were captured and routed to the appropriate on-call team. During my usage, I did not encounter any significant outages or stability issues that impacted our operations due to PagerDuty Operations Cloud.

PagerDuty Operations Cloud is highly scalable and works well with small and large environments. The project I worked on was integrated with multiple application servers and cloud resources for monitoring. PagerDuty Operations Cloud handles all the alerts from different resources and routes them to the appropriate teams. As the infrastructure grows, new services get implemented, escalation policies get defined, and schedules and teams are easily available without requiring major changes in our existing setup. This makes it suitable for an organization to manage large cloud infrastructure and multiple team supports.

When I joined this project, they had already implemented PagerDuty Operations Cloud. When I joined, the SOPs and testing were already in process. After a few days, when I was actually onboarded, many of the alerts were configured in PagerDuty Operations Cloud. I did not get the chance to work on different tools besides PagerDuty Operations Cloud.

During the initial setup of PagerDuty Operations Cloud, when I joined the project, I got a Jira  ticket listing a few of the servers where I needed to install PagerDuty agents so it could trigger any alerts or integrate with the server. I was mostly involved in the configuration part.

The setup was straightforward. PagerDuty Operations Cloud also helped us in this process. It was not directly integrated on the individual servers, but we integrated our monitoring tools and observability with PagerDuty Operations Cloud. The servers and applications were monitored through application monitoring tools such as Instana, Zabbix , and Splunk. Whenever critical alerts were generated, they would automatically forward to PagerDuty Operations Cloud through the configured integrations we set up with the application. PagerDuty Operations Cloud would notify the on-call engineers and follow different escalation policies if the alerts were not acknowledged within a specific time. Our flow was that we had EC2  instances, AWS  servers, and CloudWatch alarms, and if any alert triggered, it would send through SNS, AWS Simple Notification Service, and then to PagerDuty Operations Cloud and the on-call engineer.

We followed the documentation provided by PagerDuty Operations Cloud for the configuration part.

The documentation is full-fledged with proper details on how to configure it depending on the integration with any application monitoring tool. They specify what steps need to be followed. If integrating with servers, they mention which type of server, whether it is Windows or Linux, and accordingly, they have provided all the documents. The documentation is comprehensive and easy to understand, such that even a layperson can do the configuration part with the way they have provided the documentation.

We are not mostly focused on utilizing PagerDuty's autonomous AI agents because we are working on cloud infrastructure where we do the deployments. We have not implemented AI in our cloud to that extent. Going forward, if our infrastructure is AI-based, then we will definitely explore where PagerDuty Operations Cloud can help in that.

As of now, we do not use generative AI capabilities of PagerDuty Operations Cloud. Our infrastructure is huge, and there is a dedicated developer team working on AI-related things. They are still in two POCs, and the POC is being evaluated. If it looks good, then only we can roll this out into production because my application is customer-facing, and we do not want anything to go wrong or if the alert triggers unnecessarily due to some AI alert that did not notify us. That would ultimately cause us to lose our SLAs and SLOs, and all the other escalation matrices would come into the picture. That is why we are still in POCs as it is critical.

That part is taken care of by a different team or mostly the clients themselves. My main role is to keep the environment always up and running, and all alerts should be properly centralized and customized accordingly.

PagerDuty Operations Cloud is basically where we get the alert, and we can integrate through Slack and on-call rotational shifts on cell phones. Prior to this, we were mostly relying on application monitoring tools only and emails and Slack notifications. If an on-call shift person is not at their desk and if any alert has been triggered and no one is there to acknowledge it or look into it and take necessary action, then ultimately there will be customer impact. That is why we implemented PagerDuty Operations Cloud. Even if the on-call person is not near their laptop, they will get the call and can immediately acknowledge and report to the team that we have received a P1 call for this specific environment or that the alert is regarding a production issue. Another team member will immediately take action, so there will not be any miss.

I did not encounter any issues that required contacting support for PagerDuty Operations Cloud. This review represents an overall rating of 9 out of 10.

PagerDuty is predominantly used for our enterprise notifications for all of the incident management processes, especially the major incident management. We have many applications and infrastructure components. Earlier, we used a solution that only provided text-based communication. When we wanted to look for something with multi-channel notification and correlation capability, that is where we leveraged PagerDuty Operations Cloud .

I am currently going through the governance process to get additional capabilities onboarded. GenAI is not yet enabled since I am from a regulated organization and had to secure approvals before enabling any AI-related components. Most probably in the next two or three months, we will be enabling both GenAI, SRE agent, and the AI capabilities of PagerDuty Operations Cloud.

The ease of use is one of the key strengths. Creating the escalation policies and notification channels per user is straightforward, and it is not a requirement that everyone has the same notification rules. Users have flexibility in getting the communication they need. Event orchestration is the other part which works well for us.

Primarily, we were able to get the right people at the right time through our escalation mechanism, which is an automated switch from level one to level two. This helped us improve the overall MTTA, and the acknowledgment rate has drastically improved. For the major incidents, we were able to triage everything with PagerDuty Operations Cloud itself instead of switching between multiple tools such as Teams or other orchestration platforms. With one solution, we are able to do the triaging, and that definitely reduced the outage window and the average outage window.

We do have automations in two main ways. One is the incoming automation where we have multiple monitoring tools and systems that generate events. We ingest them into PagerDuty Operations Cloud and then using event orchestration, we create all of the respective incidents, whether they are PagerDuty Operations Cloud-only incidents, ServiceNow  incidents, or different methods we use. The other automation method is incident workflows where we are able to call out to respective endpoints for the remaining automations. This is growing at this point in time, but event orchestration is mainly what we use for the automation of the triaging.

We used to have a two-digit figure of MTTA, and now it is reduced to less than one hour.

Getting the right people on board whenever there is a major issue and dialing them individually took a longer time. Now with PagerDuty Operations Cloud, having all of the predefined rules and the orchestrations we can create, it is definitely bringing value. Bringing the right people at the right time and improving the restoration time so that we do not impact any of the business end-user services is where PagerDuty Operations Cloud definitely plays a key role in delivering the business value.

I have submitted a few enhancement requests. Dynamic scheduling is something I was waiting for almost three or four years. Finally, I believe they are coming up in a few weeks with dynamic scheduling because whenever any operations deals occur, the shift rosters will not be static. People may be rotating between different shifts, and setting up on PagerDuty Operations Cloud was a challenging task. They are in the early access stage of dynamic rosters, and I believe that will address this issue. On the reporting perspective, there is a wide variety of reports, and the out-of-the-box reports can be matured further. Though we are getting customized reports through professional services and it is beneficial, if they were out-of-the-box, then they would further help. There are plenty of reports, but still, there is maturity that can be addressed.

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

There are not many issues except during Cloudflare  or major AWS  issues. Otherwise, we do not have any performance issues. The platform is performing well.

PagerDuty Operations Cloud is scalable, but how you will take the business model matters. We are on the user license basis, so we know how many users we can onboard to PagerDuty Operations Cloud. The rest of the things are definitely scalable, depending on how you agree with them on the contractual level. There is no challenge with that unless you have not calculated or forecasted your requirement.

I used PagerDuty Operations Cloud support.

I would say they are pretty good, with regular support scoring eight or nine out of ten, and professional services scoring around nine out of ten. Both are pretty good for our business requirements.

We were using different HP tools for all of the alerting and also a solution from OnSolve, earlier called TelAlert. Those solutions were distributed and not one central solution for incident management and alerts. Now it is centralized with one of our ITSM  tools and PagerDuty Operations Cloud for both alerting and incident management.

The initial setup was comparatively easy. We had to train the people because it was a new solution altogether. We got professional services support, and they helped us move forward. We did not have many challenges on the system level. Only user experience took more time as the team needed to learn how to use and operate the solution.

I used PagerDuty Operations Cloud support.

From the pricing perspective, we got a good deal. When we took the tool, we did a comparison of the competitors and evaluated, and we are satisfied with that pricing. From the ROI perspective specific to the tool, we have not had a chance to calculate it. But overall, with the end-to-end process where PagerDuty Operations Cloud is present, I think we are almost near to getting the ROI.

We verified Twilio  and two other solutions at that time.

I would definitely ask them to do a PoC and do integrations with their existing ITSM  tools or wherever they are looking for and thoroughly verify one end-to-end testing. Taking a major incident as a simulation and performing comparison on what metrics they do internally and what additional could help them out with the new solution of PagerDuty Operations Cloud, I think these two things definitely should be tested.

PagerDuty Operations Cloud as a product, I would give an eight out of ten. The only reason I put eight instead of ten is the enhancement requests or any new features. The time to market has to be much faster than what they have at this point. Some flexibility on the customization should also be provided. My overall review rating for this product is eight out of ten.

I have been using PagerDuty Operations Cloud  for the past few months. My main use case is that I use it in my day-to-day applications. A specific example of how I use PagerDuty Operations Cloud  in my application is that I use it for hosting my agent. Hosting my agent on PagerDuty Operations Cloud helps me with my day-to-day work by being efficient in terms of scalability and managing infrastructure. It has been pretty helpful.

PagerDuty Operations Cloud's best features include scalability, managing infrastructure, and managing other services. It helps me manage other services comprehensively, and I think it is pretty good overall. PagerDuty Operations Cloud has positively impacted my organization by being effective in terms of managing the system and in terms of scalability. A specific outcome that shows how PagerDuty Operations Cloud has helped my organization is that it has improved efficiency and helped in saving a lot of time.

I think PagerDuty Operations Cloud can be improved in terms of services, such as integration with AI.

I have been working in my current field for the past three years.

PagerDuty Operations Cloud has been stable based on what we have used.

PagerDuty Operations Cloud's scalability has been pretty good because we are able to spin up different resources based on the use case and load.

We have not used customer support explicitly.

I did not previously use a different solution.

I have seen a return on investment, as I mentioned earlier; there has been a lot of improvement in terms of time and cost.

My experience with pricing, setup cost, and licensing has been quite reasonable and cost-effective.

Before choosing PagerDuty Operations Cloud, I did not evaluate other options.

I would rate PagerDuty Operations Cloud six out of ten because I believe you can add more features to make the platform even better. Regarding PagerDuty Operations Cloud's AI capabilities, I think its governance and security are pretty good, and the applications are quite secure. As for PagerDuty Operations Cloud's accuracy and reliability of output, I think the accuracy is pretty high and pretty good, and I believe it should be quite reliable, though I have not explored much on the recent AI capabilities.

I would definitely suggest PagerDuty Operations Cloud as a good platform, but it depends on your use case and the amount of scalability that you are looking for. PagerDuty Operations Cloud is pretty good and quite helpful. My overall rating for PagerDuty Operations Cloud is six out of ten.