PagerDuty Operations Cloud Reviews

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

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

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

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

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

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

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

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

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

PagerDuty Operations Cloud is stable.

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

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

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

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

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

Tech support would be rated at 7.5 out of 10.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

PagerDuty Operations Cloud is stable.

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

Customer support for PagerDuty Operations Cloud is quite effective.

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

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

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

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

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

Hybrid Cloud

Microsoft Azure

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

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

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

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

I have used PagerDuty for three years.

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

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

We considered Zoho Analytics and LogicMonitor as alternate solutions.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Hybrid Cloud

Amazon Web Services (AWS)

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.

PagerDuty Operations Cloud offers great features, including service directories, Slack integrations, incident reports, alert suppression, orchestration, team management, and permission handling such as read or write. These are the best features according to my daily experience.

The integration part stands out for us, as we have utilized integrations like AWS, Azure, Jenkins for pipeline breaches, Slack, and New Relic, along with a number of plugins that are helpful.

In the market, when comparing PagerDuty Operations Cloud to VictorOps and other services, PagerDuty Operations Cloud offers great features, particularly the simplicity of its integration plugins, which is a significant advantage.

If there are issues in our production environment, we immediately get alerts and can take action. Even if we are busy with other issues and we cannot fully monitor our dashboards, the integration of alerts is fantastic because it notifies us via phone at any time. We can react immediately based on the alert's priority and take necessary action, leveraging our understanding of the infrastructure and the type of issues.

In terms of improvements, I do not have any specific suggestions. The alert suppression and merging features look good, and overall, I see no issues.

No improvements are necessary from what I have heard, and everything seems fine. I manage PagerDuty Operations Cloud operations for my team, including on-call management and schedules, and I am happy with everything from both my colleagues' and my perspective.

I have been using PagerDuty Operations Cloud for eight years.

The accuracy and reliability of PagerDuty Operations Cloud are good, and I have no doubts about it.

Currently, PagerDuty Operations Cloud is deployed in my organization on the public cloud.

As for measurable outcomes like reduced downtime or faster response times, sometimes we have to acknowledge even low-priority alerts. One instance involved a few users on my team who did not accept a low-priority alert.

From my perspective, PagerDuty Operations Cloud is good, with user-friendly features that anyone can quickly learn, including integration processes, on-call management, and escalation policies. It is a valuable asset for my organization.

Recently we integrated our AI capabilities into PagerDuty Operations Cloud, which helps us get alerts integrated with Slack, providing information on the service directory and AWS CloudWatch URL.

We have integrated our AI agents, which provide comprehensive details such as tasks, responses, acknowledgments, resolves, and links, making it beneficial for viewing and acknowledgment processes.

I need to dive deeper into this, but as of now, the resources we are using have all the necessary functionality and everything is working well.

I provide a review rating of 8.5 for PagerDuty Operations Cloud.

Public Cloud

Amazon Web Services (AWS)

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.

The aspect I appreciate most about PagerDuty Operations Cloud is certainly the incident management capabilities. We can create our rotational shifts and on-call schedules. The way it operates has become natural to us, allowing us to create schedules for separate teams and then create escalation policies. If team one misses an alert, it goes to the leads. If the lead misses acknowledging it, then it goes to the managers. It is very easy to manage in PagerDuty Operations Cloud. Recently, it has been introduced in Datadog as well, and it looks somewhat similar, but PagerDuty Operations Cloud has been our tool for so long that we have become accustomed to it.

Auto-resolve is available, so if the alert is gone, it automatically resolves. The information it provides on the incident is valuable, so we do not have to each time go to New Relic or Datadog. It brings all the information from those tools to PagerDuty Operations Cloud, allowing us to identify the issue and resolve it.

From an India perspective, what I have been noticing recently is that in India, the government itself indicates whether a call is spam or normal. Recently, when we receive calls from PagerDuty Operations Cloud numbers, they are flagged as spam calls. This is something that could be addressed.

Additionally, PagerDuty Operations Cloud is already excellent for incident management, but if it could also provide observability capabilities, that would be beneficial. A smaller team can have PagerDuty Operations Cloud for incident management, but for observability and monitoring, we have to go to New Relic or implement our own Grafana or Prometheus. If PagerDuty Operations Cloud itself started providing some monitoring capabilities, even if not in-depth observability, that would be fantastic.

Currently, New Relic and Datadog handle monitoring and observability better than PagerDuty Operations Cloud. In New Relic, we have twelve to thirteen accounts, and we navigate between those accounts. At least sixty thousand servers are reporting to those New Relic instances. Finding our server, filtering the logs, and performing related tasks is really easy. This feasibility is not there in PagerDuty Operations Cloud.

I have been using PagerDuty Operations Cloud for approximately seven to eight years

In my experience so far, there have been no stability issues. It has always been a working tool. I have not heard from any colleagues or others that we have had any support tickets open with PagerDuty Operations Cloud, which means that things have been working as expected.

For one of our clients that I am currently working with, Coupa, the entire organization is dependent on this tool. We have centralized monitoring observability with New Relic, and for incident management, we have PagerDuty Operations Cloud. The team I am in currently is handling four SaaS products, and Coupa itself has at least thirty plus or forty plus SaaS products under its umbrella. With scalability, I believe PagerDuty Operations Cloud has been working well.

PagerDuty Operations Cloud does not require any maintenance from our end.

The initial deployment was easy, and integration with the other tools was also straightforward. We integrated PagerDuty Operations Cloud with our Slack and Jira. For one of our clients, if an incident is created in PagerDuty Operations Cloud, it creates a ticket in Jira. Then on Jira, under that ticket, we maintain all the history of the incident. Jira is particularly important because in the organization, it is the go-to tool for ticketing. If a similar incident occurs, we keep a history in Jira. Integrating PagerDuty Operations Cloud with the other tools was also quite easy.

I am not very familiar with the pricing. On an organizational basis, I have not reached that level. I am still a senior cloud consultant, but the costing and those aspects are not something I am currently involved with.

PagerDuty Operations Cloud is not currently being used for additional features in our organizations. We have not started with those features currently. This is certainly not the case for our implementation. I am particularly a customer, but my clients could have partnerships with PagerDuty Operations Cloud, which I am not aware of currently. I would rate my overall experience with PagerDuty Operations Cloud as a nine out of ten.