PagerDuty Operations Cloud serves as our centralized incident management and on-call response solution for our hybrid infrastructure environment.

We primarily use PagerDuty Operations Cloud for centralized alerting and incident response, pulling alerts from DataDog, AWS CloudWatch, New Relic, and our internal monitoring tools into one unified platform. Before implementing this solution, each team used different tools and on-call processes, which resulted in missed incidents and alerts being routed to the wrong person. Now everything is consolidated into one place, gets corrected with AIOps, and routes to the right on-call engineer based on service ownership.

We also use PagerDuty Operations Cloud to manage 24/7 on-call rotations for 12 services across four teams. The escalation policies ensure that if the primary engineer does not respond, the alert automatically escalates to a secondary contact and then to management. This replaced manual phone trees and Slack pings, and it has reduced missed pages to near zero. It also provides us with an audit trail of who was notified and when, which helps with compliance.

View full review »

I have been working in my current field for over seven years as a DevOps and site reliability engineer, and my primary experience involves managing the reliability of infrastructure platforms hosted in multi-cloud and on-premises environments. I have predominantly worked with systems hosted in AWS services, setting up infrastructure, CI/CD, observability, and completely establishing the release process where I utilize PagerDuty Operations Cloud for triage and other SRE operations.

I have been using PagerDuty Operations Cloud for over four years, and I have utilized it in multiple ways. One involves using PagerDuty Operations Cloud through enterprise services via a subscription model, and I have also used it in a project at Intel where I utilized PagerDuty Operations Cloud from AWS for approximately one to one and a half years. After that period, I have been using it as a subscription currently at IBM.

One of the main use cases for PagerDuty Operations Cloud involves handling the operation center, particularly concerning incident resolutions and triaging different incidents as part of the score platform engineering team within a central IBM cloud where various IBM cloud services are hosted. To ensure continuous reliability, automated incidents are created in PagerDuty Operations Cloud and incident management automation is heavily utilized as part of the project. Previously, I worked on integrating PagerDuty Operations Cloud with default AWS services to create incidents for different AWS services as part of the host infrastructure at Intel. Currently, I am creating different incident workflows within IBM internal cloud operations to ensure an effective incident management process, utilizing integrations with different LLMs as part of incident management, along with agentic SRE tasks that have arisen in the project.

Since I am part of a larger platform engineering team and SRE operations team, there are many incidents and services that my team handles. I handle over 26 IBM cloud score services hosted in our internal platform, where there have been many incidents related to service downtime, reliability issues, and update issues. A dedicated SRE team handles end-to-end incident management, and we wanted to automate the incident management process, especially since we receive hundreds of incidents per day, up to thousands of incidents during critical release times of different services. Thus, the manual on-call process has been automated through utilizing PagerDuty Operations Cloud.

View full review »

The most important use for PagerDuty Operations Cloud is alert notification over mobile number, email, and Slack. Apart from that, escalation policy and on-call scheduling are important features.

During night incidents, when fewer people are on-call, escalation becomes critical as people naturally become sleepy. For night shift people, we have tightly integrated the system so they receive both email and mobile notifications, including calls. In most P1 incidents, users get easily notified and we can start troubleshooting immediately, which is very important.

PagerDuty Operations Cloud is a very reliable alerting system. We can easily set the escalation policy, and the important thing is that we can easily integrate with multiple notification channels including text messaging, calling, and organizational mail. It is easily integrated with Slack integration, making it user-friendly compared to other solutions. Sometimes I think it is a little noisy, but that is something we can work on.

The integration is very smooth and user-friendly compared to other solutions. I highly recommend PagerDuty Operations Cloud to my current clients, and I have informed my colleagues working in other organizations about this solution.

For example, one client experienced a hardware issue at the EBS volume level where the EBS volume became completely full, preventing the cluster from working as expected. In that case, we received a P1 alert, and we automatically notified L1 and L2 escalation. The alerts were automatically notified, and when L1 was not working, the alert escalated to L2, who received the call and started working accordingly. They escalated to the on-call L1 as well as other L1 staff, and we all got on the same call to start further troubleshooting. In that case, our RPO and RTO for this incident was resolved in less than thirty to forty minutes, while our target RPO and RTO was one hour. PagerDuty Operations Cloud is really helpful compared to normal notification channels. It understands the incident and easily notifies all stakeholders.

The user interface is absolutely fine, and there is no improvement needed right now. I also appreciate PagerDuty Operations Cloud providing so many platforms to learn through. Their courses and certifications are quite good, and we get a deeper understanding of the tool, which helps us easily guide whoever is onboarded in the new team.

In terms of improvements to incident response after using PagerDuty Operations Cloud, we have achieved reduced MTTR, mean time to resolution. We can achieve specific RTO and RPO targets by using this incident management tool.

View full review »

As of now, in my current team, we are not working with PagerDuty Operations Cloud, but it is being used in my company. I would say I am not currently working with it, but I have used it for 4.5 years straight.

I used to work for a product-based company and we used PagerDuty Operations Cloud to alert us whenever any P0 or P1 incidents came in. It would page us in the middle of the night when we were not working.

I was part of a cloud operations team, and the product had to be up 24 into 7. Since we were not working 24 into 7, we set up alerts outside of office hours and over the weekend. We had integrated our ticketing system with Slack, and the alerts were integrated to PagerDuty Operations Cloud. Based on the rotation, whoever was on call would receive an alert whenever a ticket came in. The alert would notify the on-call person via call, email, and text with information about the ticket, priority, and issue. We had PagerDuty Operations Cloud app installed on our phones so we did not have to directly rush to the laptop. We could see the initial overview from our phone to determine what the issue was and whether it was important, and we could acknowledge it from our phone. The acknowledgement time is only 15 minutes, so it was great since we could acknowledge it from the phone without having to directly open the laptop.

We used webhooks for this setup. Tickets would come into Freshservice, our ticketing tool, and then we used webhooks to generate notifications on Slack. We had created rules in New Relic, our monitoring tool, so that it would page based on specific criteria. Basically, this was done through automation because there were a lot of services and we could not do it manually. This was not my personal experience; I was not the one who did it, but I know it was done by one of my teammates.

View full review »

The main use cases for PagerDuty Operations Cloud are incident management and handling high severity incidents in an automated way. For example, at midnight, if we get a high severity incident, PagerDuty throws alarms or notifications to our Slack or team channel so other people get notified and start working on it. Another use case is that we are also monitoring our cloud VMs using PagerDuty automation, which we have done using service integration with our cloud provider. It identifies situations such as our cloud VM going to high CPU usage or requests getting dropped, which can significantly damage the application. At that time, PagerDuty sends alerts to the respective persons, the person who is on-call.

Another use case is that we also use PagerDuty to execute some of the installation scripts using PagerDuty webhooks integration in a totally automated way. Suppose any cloud resource goes faulty and we need to ensure that the respective installation or script gets executed automatically by the use of PagerDuty webhook, so that the issue gets fixed automatically. Nobody is going to be informed or bothered, as it is a self-healing process. We also use another notification to our mobile phone for any P1, which is a high severity incident that will definitely have a business impact. At that moment, we have also leveraged this tool to get a phone call.

View full review »

I use PagerDuty Operations Cloud for core tasks only because my client completely belongs to healthcare. Healthcare is a high priority where we need to help people. I primarily use it for core tasks and sometimes for primary tasks as well.

View full review »

PagerDuty Operations Cloud serves as an alerting tool for our organization. Whenever applications or any protection systems are down, we get notified via email and mobile. My current role in PagerDuty Operations Cloud is an admin role. Whenever there is a new user or any higher management requirement to grant email access to a particular server or program, we receive the request via the team, and they mention which team they are from and their role. Based on that information, if I get one email ID with a name, I have to enable the ID, then I have to add the name to PagerDuty Operations Cloud for the particular program. When the application is down or any issue is triggered, the user will be notified via mobile and email.

View full review »

Our main use case for PagerDuty Operations Cloud is for alerting purposes whenever any kind of downtime or downstream incident happens with our application which causes any downtime, and PagerDuty Operations Cloud will alert us through calls and SMS so we can get notified and quickly remediate the issue.

A unique aspect of our main use case with PagerDuty Operations Cloud is using the Runbook flow. Whenever we experience a specific kind of incident, the Runbook will trigger automation to either remediate the issues or perform root cause analysis, thus enhancing our workflow automations.

View full review »

PagerDuty Operations Cloud is used for production incident management to automate incidents when alerts come from our tools. When we have a critical issue and receive that alert and notification, we configure it accordingly. On-call scheduling, escalation policies, and tracking MTTR improvement are areas where we interact and interrogate with the tools. This approach reduces downtime, enables faster incident response, provides clear accountability, and improves reliability.

We support different clients including JPMorgan, Wells Fargo, PL, LPL, and Bank of America, though we are not a customer, partner, or reseller. More than 300 clients use the solution. In my company, we have 21 specialists working with PagerDuty Operations Cloud.

View full review »

I handle level two operations. Whenever a major incident occurs or there is an outage, I am informed first via Splunk, DataDog, and PagerDuty. PagerDuty Operations Cloud is used for alertness, and we have configured threshold values within it. I have the mobile application installed on my phone, so I receive information about any outage as soon as it occurs.

I work at Vodafone Intelligence Services, which is a subsidiary of Vodafone. We are a UK-based company that performs level one, level two, and level three operations for all European countries and some countries in India, including South Africa, Ghana, Spain, Egypt, Hungary, and the UK. These are our major customers. As part of operations, we have a team of about 15,000 people who manage the different markets and customers. PagerDuty Operations Cloud is used everywhere across our organization, along with Splunk and AppDynamics.

View full review »

PagerDuty Operations Cloud is a multifunctional digital operations platform that meets my organization's needs.

I am impressed by this digital operations solution because it is the most appropriate tool for incident detection and alerting.

PagerDuty Operations Cloud is a very user-friendly tool, highly accurate, and an easy-to-customize digital operations management system that suits my organization's needs.

It has intelligent noise reduction capabilities that play a significant role in minimizing alert floods.

View full review »

My network operation center team monitors network alerts and digital alerts and pages engineers on-call. My team utilized this tool for supporting the customer Nike, and I led the NOC operations at Cognizant. We had various sources like Splunk, New Relic, VeloCloud, and SolarWinds triggering alerts for device failures or high CPU utilization. PagerDuty Operations Cloud correlates all events from multiple sources and triggers alerts to the respective teams based on the orchestration set for the particular event. My team handles alerts through automated processes or through manual intervention and resolves incidents. They also use it to trigger on-call engineers through SMS or email.

When we receive alerts that do not need manual intervention for 15 to 20 minutes, we have automation in place to monitor that alert and resolve it if the issue is remediated automatically. We also had automated functions to check the reachability of devices where we have on-demand ping commands in PagerDuty Operations Cloud. Event correlation helps to  action bulk alerts in a single incident. For example, if one location is triggering alerts for multiple devices, all these alerts are correlated in a single incident, and the engineer will action and resolve the alerts.

We were getting a lot of alerts on a daily basis that do not require immediate intervention. We automated those alerts to be in a different queue where PagerDuty Operations Cloud itself monitors and resolves the alert. We also implemented agentic AI use cases for device interface alerts where the alerts are triggered and not immediately actioned by humans. PagerDuty Operations Cloud monitors and performs certain actions using agentic AI. If agentic AI is not able to clear the alerts, it creates an incident and ticket to the respective engineering team. If it is able to clear the issue, it automatically resolves the alert. This automation helped in reducing a lot of noisy alerts without manual intervention, and without it, a lot of manual intervention would have been required for engineers to perform basic triage.

View full review »

We use PagerDuty Operations Cloud for monitoring purposes, as we have our own agent installed in the customer's environment across AWS and Azure, virtual machines or instances. Our monitoring agent continuously monitors the customer's environment for high CPU utilization, high memory utilization, disk utilization, and if there is any problem within the customer's environment, then we get an alert on PagerDuty. After receiving the alert, we have to acknowledge it or resolve it. If the issue is still there, then we have to work on that alert and resolve the issue, so that is part of PagerDuty.

Using PagerDuty Operations Cloud is a very crucial part for us; if we do not use it, we don't know what is happening in the customer's environment. It plays a crucial role in our organization because we have no other option for receiving any kind of information from the customer's environment. If there is an outage on PagerDuty's side, we sit idle waiting for it to be resolved. We reach out to PagerDuty's team to sort out the issue quickly, as some of our customers are very important and we have to monitor their environments 24/7 because they do not want any problems.

View full review »

We have been using PagerDuty Operations Cloud for about 1.5 to two years now.

Our main use case with PagerDuty Operations Cloud is to create automation workflows with the Gen AI capabilities present in PagerDuty Operations Cloud. We run it on our e-commerce platform to detect anomalies whenever they occur.

We want to firefight different situations, so with the Gen AI capabilities of PagerDuty Operations Cloud, whenever an issue arrives during the checkout of a customer, it immediately informs us and we create a Teams channel or a Slack channel to address the issue, determine what the issue is, and fix it immediately. It throws us alerts whenever it is necessary to keep the customer journey much more smooth and much more comfortable.

We particularly use this to avoid different incidents that the customers might face, such as payment database issues, checkout issues, or product not going into cart issues. With the Gen AI provided by PagerDuty Operations Cloud, we are able to sort out everything, get timely notifications, and make the customer's journey much more smooth.

View full review »

My main use case for PagerDuty Operations Cloud is for cloud-based operations, including incident management and resolving incident responses to reduce downtime and improve reliability.

PagerDuty Operations Cloud provides a central command center that collects data signals from various IT systems, which helps us detect high-priority incidents and reduce the noise.

In addition to my main use case, we are able to perform on-call scheduling and routing with the help of PagerDuty Operations Cloud very easily.

View full review »

My name is Dinesh Singh Negi and I currently work as a Lead DataOps Engineer in the online gaming industry. My primary responsibility is ensuring the reliability, availability, and performance of our data platform and complete production system. I work extensively with AWS services, Prometheus, Grafana, and PagerDuty for monitoring, alerting, and incident management. My team supports critical gaming workloads and data pipelines that require high uptime and quick incident response. A significant part of my role involves setting up monitoring strategies, managing on-call operations, handling production incidents, and performing root cause analysis. We drive operational improvements, and we use PagerDuty Operations Cloud as our central incident management platform to ensure alerts are routed to the right team and escalated appropriately. I have been working in operations and reliability for nine to ten years and have hands-on experience managing large-scale customer-facing environments where managing, minimizing downtime, and reducing meantime to resolution are key priorities. We use PagerDuty Operations Cloud to understand the maximum time of acknowledgment and maximum time of resolution to derive meaningful analysis from the incidents that have been triggered to different teams.

I have been working for nine to ten years in operation, production support, reliability engineering, and mixed roles during this time. I have worked extensively on monitoring, incident management, system reliability, and operational excellence while particularly supporting large-scale online platforms and data operations. For five to six years, my focus has been on ensuring high availability, managing production incidents, optimizing monitoring and alerting strategies, and improving operational processes. Throughout these years, I have gained hands-on experience with AWS Cloud, Prometheus, Grafana, and PagerDuty Operations Cloud, which are the core tools we use for monitoring, alerting, and incident responses.

View full review »

We took a subscription and started integrating many applications with it. We have integrated it with ServiceNow and also use our wiki repository by Spotify called Beacon. We onboard multiple services and integrate them with PagerDuty so that different engineering teams can update their line of escalation policy and primary, secondary, and tertiary users who are on call 24/7 or following a Follow the Sun model.

Additionally, we have integrated PagerDuty for incident commanders who can acknowledge any incident page they receive and update their responses. If they need to hand it over to someone else, they can do that as well. This is how we are actually using PagerDuty. We primarily leverage it for service onboarding. For instance, if you have created a product and need to support it, which might run on any cloud such as EC2, AWS, or Azure, the service teams or triage engineering teams have their members added into PagerDuty along with different playbooks, runbooks, and SOPs integrated with any ticketing tool such as ServiceNow or Jira, whichever you are using. On these fronts, we effectively use PagerDuty.

PagerDuty Operations Cloud has been reliable as it has never gone down in my experience; I have never seen it fail. I rely on PagerDuty Operations Cloud for on-call support for any high severity incidents or sev zero scenarios. This is a great feature, and I can update it using the mobile app because we also use PagerDuty Operations Cloud mobile app. Occasionally, I may be on call during weekends, and something might come up. For example, on October 20th, I was on leave but used PagerDuty Operations Cloud to stay in sync, even without my laptop. I could join Teams and Zoom calls and simultaneously update required documentation via Copilot and ChatGPT on PagerDuty Operations Cloud regarding different incidents. This capability was extremely helpful.

View full review »

PagerDuty Operations Cloud is a platform that helps teams manage incidents, automate operations, and ensure system reliability by bringing alerts, on-call schedules, and real-time responses into one place. When we had to push things into production, we set up PagerDuty schedules on a weekly or biweekly basis. If an issue occurred at night, a roster would pop up, and the respective engineer would have to handle that use case.

A specific incident where PagerDuty Operations Cloud helped my team was during the peak season in America when lakhs of orders were placed in December, and a major S1 severity production issue suddenly happened. If no monitoring tool had been in place, the company would have faced doomed circumstances, incurring lakhs of dollars in losses. PagerDuty came to our rescue at the last moment when nothing was happening. At 3:00 a.m. my time, I received a message and subsequently a call while sleeping, and I learned that this issue had occurred. I logged in quickly, promptly fixed that issue, and within an hour or so, the issue was resolved with minimal damage. I even received appreciation for my quick response.

PagerDuty Operations Cloud helps in similar situations because whenever some issue happens and we are not aware of it, PagerDuty comes with a flag telling us that there is an issue that needs to be fixed before it becomes a major problem.

View full review »

My usual use cases of PagerDuty Operations Cloud include acknowledging and escalating any P1, P2, or P3 incidents to the upper management or the service team, and also troubleshooting for L1 or L2 issues.

For features of PagerDuty Operations Cloud, I find it easy to use and understand, and it is very easy to differentiate the alerts.

View full review »

My main use case for PagerDuty Operations Cloud is to set up shifts for people on-call.

A specific example of how I use PagerDuty Operations Cloud for setting up shifts is for when we need to set up shifts for holidays. In our team, we'll assign people who will be on-call and create an Excel sheet and upload it to PagerDuty. It works normally, gives notifications, and everything else functions properly. It is very easy to set up and manage.

I usually discuss with my team who will be on-call during holidays, and we will set up how many people are needed. We create an Excel sheet, upload it to PagerDuty, and set up the line of who is the first person to reach, and if they miss it, then whom to escalate to. The web view and website are also very easy to use. I think this is the normal use case. Perhaps other teams are using it differently, but this works well for us. Before, it was very manual, and it was quite difficult.

View full review »

The main purpose of PagerDuty Operations Cloud is to receive alarms for real incident production critical issues. Whenever an incident happens, we get an alarm call or a phone call on our phone or through an application call, so that we are aware of the situation and know that we have to be vigilant about it and resolve that particular issue. This is the main use case of PagerDuty Operations Cloud, and it is the use case where most of the company is using it.

View full review »

My use case for PagerDuty Operations Cloud is from the SRE and DevOps team. We use PagerDuty Operations Cloud for specific alerting purposes and for the pipeline process. When we build a pipeline and it suddenly fails due to some job and issues, we receive an error. We set up PagerDuty Operations Cloud with our monitoring services, which we are currently using, Datadog. Datadog is connected with PagerDuty Operations Cloud, and whenever Datadog receives an alert or a spike or anything critical, it will trigger an alert to PagerDuty Operations Cloud, and we quickly get a notification. We are currently using this process, and we are also maintaining our on-shift call rotation. For example, on Monday, Wednesday, and Friday, I am working as a shift lead, and then on Tuesday, Saturday, and Sunday, someone else is the shift lead. Regarding MTTR and all those statistics, we can see how many alerts we received, how many alerts we acknowledged this month, and we have a timeline as well. One of the valuable parts of PagerDuty Operations Cloud is that in our team, we can have a competitive environment. For example, if I resolved the most alerts triggered and resolved this month, then someone else can do it next month, and whoever resolves the most critical alerts on time receives appreciation every month.

View full review »

My main use case for PagerDuty Operations Cloud is to set up alerts for any failures, such as when one server is down, a particular service is down, or when APIs are not responding due to technical issues, with PagerDuty triggering an alert and also calling my personal mobile number to notify me about the issue, allowing me to acknowledge that I am looking into it and take necessary actions. I can give an example of a situation where PagerDuty Operations Cloud helped us handle an incident, such as when our payment system was about to go down. During that time, we usually monitor the system manually, but there are incidents where an automated system works more efficiently than a human. PagerDuty Operations Cloud identified the issue first by alerting us that something went wrong with the servers or services, which enabled us to contact the DevOps and Dev team to identify the exact issue in our banking app, highlighting how helpful PagerDuty Operations Cloud has been from the beginning. PagerDuty Operations Cloud is very helpful for monitoring purposes, allowing us to set up multiple alerting methods such as SMS alerting, email alerting, and call alerting, all of which we commonly use, proving its usefulness across various banking services, with teams including Dev, DevOps, and SecOps relying on it heavily. View full review »

I have been working with PagerDuty Operations Cloud for more than two years, though recently, within the past three months, I have not been using PagerDuty Operations Cloud. I worked in an IT firm called Equifax, which is a credit monitoring system where you can see your credit score and credit-related products and services. I am in the software engineering department building the application, and I was supporting a few applications for the past two years, integrating PagerDuty Operations Cloud with DataDog. We set alerts on our software system such that if any software that we are serving on the cloud goes down, we receive an alert in DataDog system, and we reroute the same to PagerDuty Operations Cloud by providing our PagerDuty Operations Cloud credentials in DataDog. What we are doing is integrating PagerDuty Operations Cloud with DataDog, and that alert will be generated by PagerDuty Operations Cloud through multiple channels such as SMS, phone call, and message. If any of the systems we are hosting in our cloud goes down or any alerts that we have set up through our DataDog system triggers an event, that event sends to PagerDuty Operations Cloud, which will give the alerts through multiple channels. That is how I am using PagerDuty Operations Cloud in my company and my work.

View full review »

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.

View full review »

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

View full review »

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.

View full review »

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.

View full review »

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.

View full review »

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.

View full review »

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.

View full review »

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.

View full review »

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.

View full review »

PagerDuty Operations Cloud's main use case for my organization is the integration of alerts by receiving them via mobile, email, and SMS.

For example, we integrated AWS CloudWatch alarms. If we get any age of oldest message alert, which applies to SQS, we set up our SNS integration by providing a topic and subscription, and we give the integration URL of PagerDuty Operations Cloud. If the age of the oldest message threshold is breached, we will receive an alert via PagerDuty Operations Cloud.

Regarding my main use case, we have also integrated other tools such as Prometheus and Grafana along with Alertmanager. Via Grafana, we have integrated our dashboard metrics and created alerts if the threshold is breached. Based on those metrics, PagerDuty Operations Cloud alert will be triggered.

View full review »

We had one monitoring tool in place, and whenever an incident and alert were created in that monitoring tool, we received a PagerDuty alert from there. It was configured over the vessels, and on the ships, we have a small data center. If anything went wrong, before any crew member informed us, we tried to address it and resolve the incident. Currently, one of my clients is Coupa. We have New Relic as a monitoring and observability tool, but for the pager service, we have PagerDuty in place. I was also working for another project called HP Anywhere, where we are using Datadog as an observability and monitoring stack, but we have PagerDuty for incident alerts and notifications.

View full review »

I use PagerDuty Operations Cloud for notifying engineers of any incidents or issues in our operations or infrastructure. Most of the time on our servers, I receive alerts regarding memory, disk utilization, and CPU, so when any infrastructure-related issues arise, we trigger PagerDuty alerts to the engineers to resolve them.

My main use case with PagerDuty Operations Cloud is for resolving incidents or when I need peer help on an ongoing incident. I page out the correct relevant engineers, and in response, they join the call, which is very useful for us to resolve any incidents.

View full review »

My main use case for PagerDuty Operations Cloud is monitoring and on-call management for downtime.

Recently, we had a service go down last week, and we were alerted via PagerDuty Operations Cloud of the issue. One of our on-call engineers responded to the page and quickly resolved the problem through PagerDuty Operations Cloud app.

View full review »

We use PagerDuty Operations Cloud for one primary reason: during on-call service or when an available engineer is not present and we have any severity issue occurring in any of our production servers. We use PagerDuty to page the respective engineer, and once we page them, it triggers to their PagerDuty portal where they acknowledge the alert.

The only thing I use PagerDuty Operations Cloud for is to engage on-call engineers at the moment. We have not had a chance to explore many features of PagerDuty Operations Cloud because engaging on-call engineers is the only restricted, available option we currently use.

I have not used any of PagerDuty's autonomous AI agents so far because whenever I need to engage somebody, it works fine and as expected. I wanted to check if an AI agent is already pre-installed in PagerDuty Operations Cloud, but I have not used PagerDuty's generative AI for providing insights for decision-making.

I use PagerDuty Operations Cloud web portal very infrequently. I do not know if the AI tool is already integrated into PagerDuty Operations Cloud. If an AI tool is not yet integrated, a chatbot could be added. If I cannot find any of the engineers in any of the assigned groups, I could ask the chatbot or inquire which group a specific person is added to, and it could give me the group name so I can directly go to that group and page that engineer. I do not know if that feature is already implemented, but this is my idea.

My management deals with PagerDuty Operations Cloud pricing and licensing. When I started working at my current company, PagerDuty Operations Cloud was already in place.

View full review »

In my organization, we use PagerDuty Operations Cloud to acknowledge alerts. PagerDuty Operations Cloud is organized so that it is often used to page the SMEs. Whenever we work on any tasks and face critical situations where we are unable to troubleshoot from our end, we page for the SMEs. Irrespective of the team, if it is infra-related issues, we page to infra. If it is related to some other product, we page to that product's SMEs and involve them into a PagerDuty Operations Cloud call. We inform them regarding the issues, and then they acknowledge the alerts. After acknowledging the alerts, they start working on that particular error.

PagerDuty Operations Cloud is also organized so that if there is any critical issue, it will create an alert that will go in a particular notification form to the SME with a phone call, stating that there is a critical issue which is in progress. The particular SME will acknowledge the alert and come and join the call, mentioning that they have been paged for this issue. Then we will start working with that particular team to resolve the issue from our end.

Regarding the incident command system, we use the Freshservice tool. Freshservice and PagerDuty Operations Cloud have been synced in my organization. The incident command system is a structured way for major incidents. Whenever there would be any outage, in order to proceed with the communication flow, we use the incident command system in PagerDuty Operations Cloud. Everyone will jump into a call, and then multiple people will start fixing the issues. Everyone will be working hard to bring that instance back online or to restore that particular environment.

View full review »

I have been in my current role for the past 18 months, and we started using PagerDuty Operations Cloud earlier this year around January or February to manage our operations.

PagerDuty Operations Cloud's primary use case is alerting. We switched to ensure alerts are efficient and effective so that the on-call engineer does not miss any alert. We instrument many alerts on it, including VPN downtime, transaction monitoring, success rate, and latency. We configured PagerDuty Operations Cloud so that if any of those metrics are met or if any of those SLOs and SLIs are breached, we can quickly take action and resolve the issue. For day-to-day use, we run a 24-hour shift where all shifts are entered into the system, and every on-call engineer uses PagerDuty Operations Cloud to receive alerts. Beyond alerting, we also use scheduling, incident management, and incident reports.

View full review »

As a customer, I use PagerDuty Operations Cloud for my typical operational needs.

View full review »

My main use case for PagerDuty Operations Cloud is targeted alert paging.

A specific example of how I use targeted alert paging with PagerDuty Operations Cloud is that we were able to tie our services and use PagerDuty AIOps to understand dependencies so we get paged a minimal number of times as opposed to an alert storm.

View full review »

PagerDuty Operations Cloud is used to understand whether there are false positives or false alerts because it is integrated into a system where there would be a phone number, such as anyone from the team's phone number or perhaps the shift supervisor's phone number. Once those triggers are there, it would hit that number until somebody picks it up and acknowledges or escalates the alert or threat.

In a recent incident through PagerDuty Operations Cloud, there was one issue with one appliance that was continuously going wrong. Even if we were acknowledging it and closing it and had denoted it as a false positive and a false trigger or false alarm, it was still continuously hitting us. There was some issue with the appliance or some issue with the server. Once we understood that, we escalated this to the company's SecOps team, and they had to go inside to find out more details. PagerDuty Operations Cloud team was coordinated with them. Once they were coordinated, they could dig in deep and find out what the issue was. A high-priority P1 ticket was raised for that as per ITIL principles.

PagerDuty Operations Cloud was being used inside the office only, and if we enter anybody's number, for example, it would continuously be hitting at any time whenever the alerts are there. Whoever's numbers are added, such as a shift supervisor or shift people, those would keep on hitting back.

View full review »

We receive a notification if there are any failed jobs or operations. We have some Bamboo agents working, so if one of the jobs fails on one of these servers, PagerDuty Operations Cloud creates an incident and notifies us. We use PagerDuty Operations Cloud for monitoring purposes, and it works great for our current needs.

View full review »

My main use case for PagerDuty Operations Cloud is incident management, as we use it for alerting people who are on call.

I definitely use PagerDuty Operations Cloud for incident management; we have set up the account, schedule, teams, etc., and we continuously monitor our logs for any anomalies with proactive alerts. We define priority because we don't want to alert people on the phone unnecessarily, thus we categorize alerts based on severity and business disruption, sending information via the integrated APIs to the relevant teams, specifying whether to communicate through Slack or phone based on the severity.

This is the main use case we have; it's a tool that last mile connect kind of people use.

View full review »

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

View full review »

We use the solution for incident management.

View full review »

The solution is used to alert the on-call users if we have priority-one or business-critical issues.

View full review »

Our use cases include generating alerts from our site 24/7. We are managing the cloud infrastructure there.  

View full review »

We have a support team consisting of roughly 20 support agents, and we used PagerDuty to raise alerts to people on the roster. It was integrated with our help desk ticketing system and AppDynamics, which we use for application monitoring. 

There were rules in place for when AppDynamics generated an alert. For example, if a transaction is slow or something is about to go down, PagerDuty would notify the IT team members to look at the issue. 

View full review »

It's mainly for IT call scheduling, emergency contacts, events, and those kinds of things. It's integrated with AWS, MS Teams, Remedy, and other solutions.

View full review »

We primarily use this solution to track alerts from our cloud environment and monitor and respond to alerts on our cloud platform.

View full review »

I interact with customers and then see the use cases and how they would use the PagerDuty tool and the integrations that come with it. I basically see how the customers will use the product. I then have conversations with the higher members or the stakeholders in the company on what ROIs they would get from this tool and the measurements of metrics, etc.

View full review »

We use PagerDuty for alerting and escalations. We have it integrated with our monitoring tools.

View full review »

I use the solution as for log aggregation, scheduling, and filtering out false positives. 

View full review »

We use PagerDuty for incident managment. We're looking at integrating PagerDuty with Rundeck in the future.

View full review »

The primary use case of the solution is to alert the on-call person when there are any critical errors or when the servers are down. It is also used for the on-call scheduling of personnel.

View full review »

The two major use cases were alerts for events and scheduling of engineers to get pages based on incidents.

View full review »

I tie alerts from our GCP tenants to PagerDuty.

View full review »

I use PagerDuty for incidents, event orchestration, alerts, and creating services.

View full review »

We are a 24-hour online business. We use it for scheduling our on-call engineers and making sure that there is follow-the-sun or round-the-clock coverage for alerting and network operations.

It ingests all our alert paths, i.e., anything that generates an alert of any description, such as, Splunk, AWS, and internal applications. We feed all our events into it, then it generates alerts which need a response from an engineer with a description. Another thing is it is built-in scheduling is pretty much hands-off for our on-call engineers unless somebody goes on holidays. That is the only time that we have to jump in there and make any changes.

View full review »

We use this solution to alert us to system errors.

View full review »

We mostly use it for our on-call engineers, for schedules, alerting, and critical alerts. And, of course, we use it for the management of an issue, so that people acknowledge the alerts, reassign them, etc.

View full review »

The most common use case is the result of alerts coming from a monitoring system, like New Relic or Nagios, alerts that we define as critical. They are alerts where we need someone to get on a bridge or to start working on them during the night. Once such an alert is firing, it fires a PagerDuty alert and it triggers the current on-call who is scheduled in PagerDuty's schedule.

The on-call person acknowledges the alert and looks into it to understand what is going on and to update, via PagerDuty, what the status is. The update will be sent to all the groups that are part of the PagerDuty schedule until the issue is resolved.

We mostly integrate it with other monitoring tools like New Relic or Nagios, or we are using their email integration for on-call processes to page people in groups. We also use it for Sev 1 issues that are coming from alerts from New Relic or from Nagios or other monitoring systems.

View full review »

Our primary use case of this solution is for alarming and to mitigate threats in our organization.

View full review »

We use the product for intrusion management.

View full review »