One of the features I find valuable in PagerDuty Operations Cloud, which is part of our current migration activities, involves automating the entire incident management process by integrating all service incidents into a single incident management page. In IBM cloud, since many services and incidents occur, I utilize the runbook automation feature where I create runbooks for each service and common issues that facilitate incident management for common incidents.

The runbook automation positively impacts my team's workflow by significantly speeding up the incident resolution process. In IBM cloud, we have different services hosted such as IBM Schematics and IBM Kubernetes Service, with thousands of concurrent global users. We face several issues during multiple incidents, particularly in reliability and infrastructure side issues. Basic level zero incidents often require simple commands run in kubectl. Therefore, I created runbooks to address these common issues, allowing SRE team members to refer to the runbook and manually fix the issues. However, before using PagerDuty Operations Cloud's runbook automation, it took over 20 minutes to resolve these issues. After implementing PagerDuty Operations Cloud's runbook automation, I have reduced the response time from over 20 minutes to less than two minutes, saving approximately 80 to 90 percent of the time and making mean time to resolve significantly faster. I review the runbooks quarterly to update them with any new steps necessary.

PagerDuty Operations Cloud has greatly improved our productivity. Previously, I handled many incidents with manual automation runbooks, leading to substantial toil for the SRE teams in resolving even minor incidents and complicating our on-call schedule. Once I adopted PagerDuty Operations Cloud and heavily utilized the runbook automation, I provided a list of common incidents to PagerDuty Operations Cloud, which then did the heavy lifting in fixing basic incidents automatically. This allowed my team to focus more on development activities related to platform engineering. Overall, it has reduced our toil by at least 50 to 60 percent and improved our efficiency, enabling us to onboard more services. We increased from onboarding seven core IBM cloud services to over 28 services now hosted.

The expansion of services impacts our organization's goals and customer experience by allowing all IBM cloud internal services to be hosted on a dedicated platform engineering service called Rednote. Before using PagerDuty Operations Cloud, I utilized Nagios and Sysdig, and after migrating to PagerDuty Operations Cloud last year, I prepared a set of runbooks, automating on-call schedules and incident management. This automation has led to a significant increase in incident closure rates from around 40 to 45 percent, improving efficiency and reducing manual toil for basic incidents by about 60 percent. This enables my team to focus more on development activities as basic incidents that can be managed through simpler runbooks are now handled automatically by PagerDuty Operations Cloud. Additionally, incorporating AIOps into our on-call scheduling and notifications helps it learn from previous incidents and proactively address issues. This scalability has allowed me to grow from handling four cloud services to 28 services, increasing from 200 to 300 customers to over 1800 plus customers, thanks to PagerDuty Operations Cloud.

View full review »

The valuable and useful features of PagerDuty Operations Cloud were reliable alert notifications. It was good for on-call scheduling. Whenever there is an issue, we used to come up when there is an issue, so we used to call that shift as on-call. That was a pretty good thing with PagerDuty Operations Cloud. The integration part was also quite very good with this application. These are some amazing things which I really appreciated with this app.

View full review »

PagerDuty Operations Cloud helps our team respond by increasing our response time. Whenever there is any incident, we will get notified and through PagerDuty Operations Cloud, we receive calls 24/7, allowing us to instantly get into a call or investigation and remediate the issue as early as possible. This way, PagerDuty Operations Cloud helps us reduce the MTTR and ensures our application is more reliable and resilient.

We have been using the Runbook automation feature for building automated flows that help us add extra monitoring for specific alerts or incidents and perform remediation tasks autonomously using this Runbook flow.

One feature I particularly appreciate about PagerDuty Operations Cloud is that it offers multiple notification options. I receive alerts via call as well as SMS, which is beneficial. If I miss the call, I may still receive the SMS and vice versa.

Through PagerDuty Operations Cloud, our MTTR has been reduced by at least 30% over the last year due to its instant notification features like SMS and calls, which help us jump on calls quickly to remediate issues. This reduction has impacted our application downtime, ensuring an uptime of approximately 99% throughout the year.

View full review »

The integration with ServiceNow is one of the most valuable features. I rely on PagerDuty Operations Cloud for on-call support for high severity incidents or sev zero scenarios, which is a great feature. PagerDuty Operations Cloud has been reliable as it has never gone down, and I trust it for incident response. Additionally, I find the capability to update using the mobile app extremely helpful.

Our developers noted that integrating incident bots or chatbots created with AI tools occasionally presents challenges with PagerDuty Operations Cloud. This is the only negative feedback I have encountered. However, I am very satisfied with PagerDuty Operations Cloud because my team is also pleased with it. We have onboarded multiple teams using this tool, and it functions well. From a security perspective, I believe there could be more layers. When scheduling on-call rotations for different team members, access should be restricted to specific users to prevent unauthorized changes to the on-call module. Despite this, the security features have been functioning well, and overall, I appreciate PagerDuty Operations Cloud.

View full review »

Some of the best features PagerDuty Operations Cloud offers are comprehensive incident management, automation, and AI operations, all integrated into one platform. Second, it provides noise reduction and smarter alert grouping through global intelligent alert grouping that uses machine learning to group and correlate alerts across services. It also provides automation to reduce toil and speed up resolutions and artificial intelligence, including generative AI assistance, to help teams respond faster and smarter. Additionally, it has built-in workflows with standardized, repeatable processes, improved visibility, collaboration, and a unified operations view, and support for bridging customer-facing teams and engineering and the SRE teams. The last thing it provides is scalability for enterprise environments.

The AI-powered alert grouping and automation have made a difference in my day-to-day work by reducing alert noise. It automatically groups multiple related alerts into a single incident, so instead of 20 separate alerts, I get one meaningful alert, which prevents on-call engineers from being spammed. It also helps in faster root cause understanding because AI looks at patterns across systems including logs, metrics, alarms, and graphs, finally providing a broad summary about that. This cuts down the response time, helps in prioritization, and reduces the burnout of on-call teams.

PagerDuty Operations Cloud has positively impacted my organization by helping in faster incident detection and resolution with less downtime. It has reduced noise and fewer false alerts, allowing better focus for teams, meaning that on-call engineers can focus only on real and important issues rather than all the duplicate and negligible issues. It has helped with automation and efficiency, better collaboration and communication among teams, improved post-incident learning and prevention, and has not only helped in operational cost savings and better return on investment, but also in scalability and readiness for growth.

View full review »

The best features PagerDuty Operations Cloud offers are that it is simple to set up and supports Excel sheet uploads, which was very helpful. Setting up notifications and the integration with Datadog was excellent. We can automate many things.

PagerDuty Operations Cloud has positively impacted my organization because the support team is very happy. Before, setting up everything was very difficult. Now, we don't have to think about it. We can simply set it up in PagerDuty and it works. The escalation and everything simply works with the configuration we set up six months to one year ago, and it still functions. We make only minor changes. I think a lot of manual effort has been reduced, and the system is more reliable.

Since implementing PagerDuty Operations Cloud, before the L1 team had to stay online at night, and if someone fell asleep and missed an issue, it would easily escalate to a manager or someone higher up, creating a lot of fuss. That is almost gone now. The discussion part about deciding who will be on-call and setting that up was not as foolproof when we were creating it manually, and someone had to invest a lot of time, around one or two hours weekly. Now, it takes simply less than five minutes. Every week, we simply discuss and it's done. I think a lot of time has been saved, and a lot of mental effort has been saved.

View full review »

One feature of PagerDuty Operations Cloud that I find valuable is the on-call schedule. We can manage our on-call scheduling, and we have various alert and notification delivery methods available, including mobile. We can receive phone calls, emails, SMS, and push notifications. For example, if someone missed the notification, they will get a phone call, which is very straightforward. We also have incident automation, making collaboration with any third-party monitoring services we use very straightforward, such as Datadog. We can seamlessly automate things with PagerDuty Operations Cloud. The AI features are also beneficial; for example, noisy alerts that trigger regularly and false positive alerts get suppressed. It checks the past month's alerts, showing us that this alert triggered 60 percent, this alert triggered 20 percent, this alert is rare, and this alert is not rare. The escalation policy is excellent as well, as if I did not pick up the call, my manager will get the call; if my manager did not pick up, then his manager gets the call. These are some of the most valuable parts we use in PagerDuty Operations Cloud.

In Datadog, we have multiple dashboards and monitoring systems where we see our spikes and alerts. When we integrated with PagerDuty Operations Cloud, we got better signal and less noise. When we are seeing a spike that is concurrent, in PagerDuty Operations Cloud, the AI feature already signifies that alert as a noisy alert, and it suppresses that alert. This significantly improves our workflow with both Datadog and PagerDuty Operations Cloud. We have faster response and faster escalation. Previously, in Datadog, we did not get notifications, and people would refresh it and check the spike every hour. Now that we integrated PagerDuty Operations Cloud, any alert triggers, and we quickly get a notification or a phone call. Therefore, we do not sit in front of a computer and refresh repeatedly. Additionally, we have a centralized incident workflow; PagerDuty Operations Cloud and Datadog feed into PagerDuty Operations Cloud incident timeline, so we see everything there. We do not need to open Datadog again and again, and if we need to deep dive into an alert from Datadog, we can click the link inside PagerDuty Operations Cloud, redirecting us to the Datadog dashboard where everything is noted down and visible.

In PagerDuty Operations Cloud, AI suppressing our alerts has helped streamline repetitive tasks. For example, very noisy alerts get suppressed automatically, aiding smarter routing. When we have new joiners in our team, they see alerts already suppressed, allowing them to focus on the critical ones instead of the lower ones. Additionally, alert prioritization is present; we receive critical alerts, high alerts, and then low alerts. The faster prioritization facilitated by AI enhances our alert management processes. Also, the root cause historical pattern assists us; if we get an alert similar to one from last month, it tells us how we resolved that alert previously. Historical patterns using AI greatly aid us in alert management.

View full review »

The best features of PagerDuty Operations Cloud include the SMS and call alerting functions, which I find very beneficial compared to other tools I have used, such as Coral Logics and Sumo Logic, which primarily focus on email alerting. PagerDuty Operations Cloud goes a level beyond by notifying users through SMS and calls, allowing us to tag the concerned teams to address specific issues promptly. In addition to those features, I also find the integration and reporting aspects of PagerDuty Operations Cloud valuable, as it records all triggered calls and incidents, enabling us to analyze patterns and identify the times when systems go down, thus assisting us in understanding and addressing the underlying causes. PagerDuty Operations Cloud has positively impacted our organization by ensuring that our banking applications, which operate 24/7, remain functional and efficient, contributing to better service availability. View full review »

The best features PagerDuty Operations Cloud offers include the ability to integrate its app through various platforms such as Teams and various monitoring platforms such as New Relic and DynaTrace. It is easy to use, easy to log in and configure your on-call rotation, as well as utilizing their business services and technical services to properly configure how you want things monitored and alerted.

The integrations and easy configuration help our team by saving time and reducing errors. We use Terraform to create various modules, including integrations with PagerDuty Operations Cloud and our monitoring platform, New Relic. When a team creates a new application, we ask them to use our monitoring module to monitor their service using New Relic and PagerDuty Operations Cloud. By doing that, we save time and errors by preventing people from manually having to set up their PagerDuty Operations Cloud operations; it is all done through this module, which is easy to use.

PagerDuty Operations Cloud has positively impacted our organization by allowing us to be immediately paged when a system or service is down, enabling us to quickly respond and provide updates to the organization on issues and their resolution.

This quick response has led to measurable improvements, with reduced downtime and faster incident resolution times, as our on-call engineers are appropriately alerted when things happen. We understand based on the page what is going on and how to quickly respond to it, and if we need help, we can loop in other engineers and our managers that own the product to resolve it quicker.

View full review »

The best feature that I like about PagerDuty Operations Cloud is whenever we page a particular team. There is a specific feature where we can directly page a person. Usually, once we trigger the alert, it goes to a particular person, and if that person does not acknowledge it, then it will go to their reporting person. Even if they also do not acknowledge it, then it will go to some other person. In that case, it tends to take a bit of time because whenever we see the alerts, the alerts will be shifting to other people. Some people might not acknowledge the alerts due to various reasons, and it may get missed. In PagerDuty Operations Cloud, there is a specific feature where we can page a specific person or a specific user. If we give the particular team name, then in the subfield, we can specifically page a person. This feature attracts me a lot.

Additionally, there is another feature where we can check the SME calendar. In my organization, for a particular week, one person will be allotted as an SME. That calendar shows which person is the SME for the particular week regarding the particular product. These are the features I enjoy the most in PagerDuty Operations Cloud.

The main benefits I can say from using PagerDuty Operations Cloud are that we can easily page them. It is also widely used in our operations team for faster incident response, leading to a reduction of the MTTR, mean time to resolution. The smart on-call management allows us to create a call for the on-call people and to involve the backup engineers as well. One special thing in PagerDuty Operations Cloud is it has time zone-based scheduling. As per that particular time zone, we can schedule them. I witnessed automated escalation, where the particular person missed acknowledging the alert in PagerDuty Operations Cloud, leading to an automated escalation to their associate director or VP. This escalation policy is also very good in PagerDuty Operations Cloud.

The impact of integrating PagerDuty Operations Cloud with Freshservice is very good because earlier, when it was not integrated, there were many problems while paging the alerts. Now, when we have integrated it to Freshservice, once the alert comes into the queue of Freshservice, automatically a PagerDuty Operations Cloud alert will be created. So automatically, it syncs. Once it gets synced, the alert will be automatically created in PagerDuty Operations Cloud and will go to that particular person who is allotted as an SME for that particular product.

The measurable benefits from PagerDuty Operations Cloud are that it has made our work easier, where the alerts will be synced and then directly create an alert to the SMEs. Instead of doing it manually, if it is automated in such a way that an alert gets triggered and routed directly to the SME, then that is a great benefit.

View full review »

The best features of PagerDuty Operations Cloud include alerting, which is very important and the main reason we retain it, and scheduling as well.

Initially, we used Excel to manage our on-call engineers' schedules, but with PagerDuty Operations Cloud, it shows when you are on duty and allows other team members from different teams to check who is on duty without needing to ask. This has significantly reduced the time spent on checking who is on duty by providing visibility at each point.

Scheduling with PagerDuty Operations Cloud has reduced confusion because we set it up with a round-robin rotation, and nobody needs to update it every day unlike with Excel, where we had to create a new schedule every two months. Now we only make changes when necessary, making the process more efficient and organized for on-call engineers to know when they are on duty. The system also alerts them in advance for their upcoming shifts.

View full review »

The best features that PagerDuty Operations Cloud offers are that it is user-friendly, the design is scalable, and it is quite easy to use for a newbie as well. Logging into the alerts as well as logging into any details are easy over PagerDuty Operations Cloud.

It is user-friendly because it does not need any sort of coding or any sort of scripting language to be filled in. It can just operate with mouse clicks. We need to know how to operate it, when to close, when not to close, and how to read green, yellow, red, and blue monitors or markers as per the monitoring.

It is easy to use, and I think the software also comes at a very low budget or low cost, which is very cost-effective and cost-friendly as well, rather than its alternatives. It benefits in every way, in network security, in cybersecurity, and overall company data monitoring and firewall as well.

I do not have any specific numbers because those will not be shared with us. This is confidential information. The response time is great, and after using PagerDuty Operations Cloud, false positives and false alarms, as well as security monitoring, were very strongly done.

View full review »

The best features PagerDuty Operations Cloud offers include quick access to failed jobs and the ability to add descriptions about the failed job. The quick access allows us to rapidly identify which job or operation has failed because it sends the job name or the operation name that has failed.

I have heard that integration between our systems and PagerDuty Operations Cloud was easy to implement. For efficiency, we can monitor our deployment process in real time. For incident response, PagerDuty Operations Cloud creates alarms that make calls to the specific person who can handle these issues.

We have fewer missed incidents because it keeps calling regarding the incidents until they are resolved. We have also reduced downtime because we notice errors and failed jobs, and we work to fix them.

View full review »

The best features of PagerDuty Operations Cloud include integration, mobile app, reporting, and analytics, which I find very useful based on the access I have.

We review the data periodically to see our performance; for example, we check for alert fatigue, how many alerts have been addressed, and our TDX metrics such as time to respond. The analytics of PagerDuty Operations Cloud is so good that it gives me good visibility with just a few clicks, which helps in discussions with the team for continuous improvements.

View full review »

The product used to be unique in getting the message to the right person to fix the job. It integrates with multiple applications and is highly customizable, with policies, escalation procedures, and an event routing tool that ensures contacting the right person. A significant advantage is that it includes a metrics overlay, which provides an overview of what is happening in the environment, and its scheduling capabilities are superior to other operations.

View full review »

PagerDuty helps you bifurcate teams and redirect alerts to specific teams. It has good user management and is easy to plug in. It has good APIs to integrate with our apps and send alerts, making it compatible with most applications. It becomes a powerful infrastructure when handling priority applications, so we use it during the critical phase of our engineering development.

View full review »

We found that the interface of PagerDuty is more friendly. It was easy to use and easy to set up. It integrated easily with our critical server and our Jira project console. It also had better features than Opsgenie. We were impressed with PagerDuty, so we decided to give it a try.

View full review »

PagerDuty let us set up rosters based on our shifts. We could assign a hierarchy for how the calls should be escalated and the number of times the call will be transferred between people before it is answered. It makes it easy to access an agent via mobile phone.

View full review »

The most important feature that is used is call scheduling. We are also able actually to call IT folks in the case of an emergency.

I have not heard anything bad about its stability.

It has scaled well for us.

View full review »

The SMS pages and the mobile application are pretty much the top two features.

View full review »

The ease of having it on a mobile phone is valuable. We can always track incidents wherever we are, even away from our computers. Additionally, the escalation feature for incidents to senior engineers or other people is very useful.

View full review »

The inbound integrations that PagerDuty provides with most of the DevOps tools are valuable. 

It's an incident management tool. So, its main functionality is to integrate with monitoring tools. There is a flexible and easy way of integrating with monitoring tools. That's what I have observed in most of the scenarios. It allows us to configure the integration with APIs and plugins as well.

View full review »

The most valuable features of PagerDuty are customization, access, policies, and different rules regarding the path of escalation. Additionally, it's easy to use and create overrides. For example, if you all are on a call for one week each, but somebody wants to go on PTO,  the team needs to swap shifts in PagerDuty. This is easy to do by creating overrides to switch up the set schedules. It's very user-friendly in that aspect. It works well for monitoring and alerting.

View full review »

The most valuable feature is the phone app that allows us to send notifications without additional fees when sending by SMS or phone calls. There is also an escalation metric that allows any alert that goes unanswered to automatically move on to the next person on the list.

View full review »

Alert deduplication and noise reduction for alerts are the major features that I found useful.

View full review »

PagerDuty's best features are the dedicated application that allows me to reach my engineers immediately and the ability to directly assign specific tasks to individuals and have them report back.

View full review »

The most valuable feature of PagerDuty is its integration with other tools, such as Amazon AWS, to receive notifications or create automatic instances.

View full review »

 The alerts are immediate in this solution, which allows us to respond to errors quickly.

We are also able to set the escalations level in this solution, which is useful.

View full review »

The solution's most valuable features are that it adds each alert as a service, has good scheduling capabilities, and includes the ability to write logic based on texts. 

View full review »

PagerDuty's notification process is the most valuable feature.

View full review »

The scheduling feature is the main valuable one for us, because it was previously costing us time. For example, when I was doing the scheduling for the rosters, I would be spending maybe a day out of a month getting the rosters all sorted out. It was rather intense, and a fair chunk of time each month was dedicated to the schedules.

The flexibility in what we can send to it: emails, custom webhooks, and things like that.

We have our production and development environments. If an alert goes offline in the development environment, it's generally treated as a low priority. However, if anything goes down or alerts us from the production environment as a critical or high priority, then an engineer has to stop and fix it straightaway. 

View full review »

It's a tool for incident management, to help us understand what happened during an alert. A cool feature is that it helps us to understand the flow of the alert. If the alert was coming to the current on-call and he didn't catch the call or didn't notice it for any reason, it starts being escalated automatically, according to the escalation schedule, or to other teammates. You can see the flow very easily on your phone or via the website, if you want to do a post-mortem.

The solution’s alerting functionality is very good. It does the job. It's not that it only works sometimes. It works every time it needs to. It also knows how to close alerts that are closed from the monitoring system and you can easily close and acknowledge alerts via your phone even if you don't have the mobile app. You can do it with an SMS. So at 2:00 a.m., it's very easy to navigate an incident.

The email-for-alerting integration is also valuable. If there is a team that needs my team, they can easily send an email with the subject and why they want us to be on board and that we should start investigating an issue. Instead of how it worked in the past, when they would call the on-call number and start talking and try to explain what is going on, they just send an email and it pages the current on-call who is scheduled. It's very nice and easy.

While using PagerDuty hasn't resulted in a decrease in issues, it has allowed us, in combination with the monitoring systems, to know about issues before customers are alerting us. If a monitoring system was only sending emails, those emails could be missed among thousands of emails. But if we create alerts in New Relic, which integrates with PagerDuty, and we get a call from PagerDuty, it's much better. By not missing an email, it allows us, during working hours, to engage with other teams or to resolve the issue without causing problems to our customers. Issues can be resolved before someone notices.

It is more the monitoring systems that can point out problems to be addressed before they become worse, but those systems are not really able to do more than send us an email. Without the integration to PagerDuty, issues that are defined as critical could be missed.

View full review »

The product easily integrates with other solutions. We can do automation. The product is used for alerting.

View full review »

The most valuable feature is definitely the flexibility of the schedule. 

The mobile app is quite also good for what we do: for receiving alerts, acknowledging, assigning, adding new responders. It has rich features for our needs.

The alerting functionality is quite good. It is one of the key parts of our on-call process, so that people can react when things are not working as expected. We trust it a lot. It definitely works well. We have never missed alerts or had situations in which we felt that we could not trust the alerting functionality of PagerDuty. Alerts in our environment could be caused by a specific part of the platform not running right. If a database goes down, for example, we will get an alert. There could also be errors in an application or a particular zone of infrastructure is down, or if service-level objectives are being affected for some reason. In all these cases, we will get alerts.

View full review »

The feature I like the most is the alarming.

View full review »

Obviously, scheduling the calls is a valuable feature. We have a feature where there were three calls: primary one, primary two and primary three. If this guy doesn't pick up, it will respond a certain way; that's the most valuable feature. We use it on the weekends. If some customer escalates, I'll get a page, if my manager doesn't pick up. That's one of the great features; I love it.

View full review »

Notification is the most valuable feature.

View full review »

We email in, and Pager Duty finds the person on-call, alerts and escalates.

View full review »

The outbound calling feature is a feature that I find a lot of value from.

View full review »

Whenever we have a server that goes down, we get notified immediately which helps out our clients and all the developers, so we know when we have to log on to bring it back up.

View full review »

When I first started at this company, we set up our AD for free on Mail Server, but it paged everyone who was on-call. Moreover, we couldn't make adjustments, such as adding and removing people. The result was that if you didn't respond to a page, the task wouldn't get done.

With PagerDuty, if you don't respond to a page, the next on-call person would get the page. We don't have to think about who is on-call because the process is automatic.

View full review »

I've found the the versatility of notifications to be the most valuable feature. With the multiple methods of notification and the escalation policies, we can always be certain that someone will get the message.

View full review »

• Easy to ACK
• Easy to read UI
• Custom notification
• Easy to override schedules for on-call swaps
• Easy integration with Nagios

View full review »

• Automated scheduling
• Escalation
• Text to voice

View full review »

I really like the reporting aspects of the solution; they are absolute.

View full review »

Its alerting capabilities, simple user interface, stability and functionality is exactly what we need. I would also highlight a fact, they have very responsive support, and API developers support. We mainly use it at GoodData for:

A) Alert/event routing from our product/monitoring system to the responsible DevOPS engineer who is on duty to fix/workaround issues reported. We mostly escalate to mobile/cell phones.

B) We use it for on call schedule resource planning as we have around 100 people using PagerDuty (mainly from engineering, support, services). Using their system, you basically know at any time who is working, when and which service he owns/is responsible for.

C) Billing/accounting. Using their APIs we are able to easily financially compensate those 100 people for their on-call duties. This might be country/geolocation specific.

View full review »

Push notifications to mobile devices combined with the in-app ability to override the system volume allows for flexibility in managing other device notifications, while high-level notifications can be alerted without worrying if your device's notification level is sufficient.

View full review »

SMS + phone call alerts, multiple escalation lists, personalized notification rules, centralized administrator interface, automatic incident creation. The customization options available in PagerDuty make conformity to our needs possible.

View full review »

I would say the notifications, and the information that comes along with them.

View full review »

There are several valuable features that we use, among them are the escalation policy, integration of email, telephone, and mobile app.

View full review »

The product has valuable on-call scheduling, escalation, and incident workflow management features.

View full review »