What is our primary use case?
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.
What is most valuable?
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.
What needs improvement?
In terms of integration, while I cannot speak for all developers, some have encountered anomalies, but I expect they will resolve over time. 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.
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.
For how long have I used the solution?
I have been using PagerDuty Operations Cloud since 2021.
What do I think about the stability of the solution?
I cannot recall ever having to contact support. I have been using PagerDuty Operations Cloud for more than seven years across two organizations without ever needing assistance. It never breaks down for us, and considering I have devoted 20 years of my career to IT infrastructure operations, where everything typically breaks down, including Jira and ServiceNow, it is impressive to say that PagerDuty Operations Cloud has not caused disruptions. I can also mention MongoDB Atlas as a vendor we subscribe to and similarly, I have never experienced disruptions in their services, aside from scheduled maintenance.
PagerDuty Operations Cloud performs maintenance, which we are notified of in advance, usually two weeks prior, and this occurs during low-activity periods such as holidays. We adapt our workflows accordingly but typically, these notifications for maintenance are infrequent, occurring once or twice a year, making them manageable.
What do I think about the scalability of the solution?
PagerDuty Operations Cloud is scalable, but I emphasize I am a user. In our field, whether supporting applications or web technologies, it is very scalable. However, if developers assess it from an AI perspective, I cannot comment due to our newness to AI. Nevertheless, I find it scalable in all other aspects and have worked with some of the top tools available, apart from Remedy, Siebel, or Lotus Notes. Overall, it is highly scalable.
How are customer service and support?
I cannot recall ever having to contact support.
How would you rate customer service and support?
Which solution did I use previously and why did I switch?
I have never used any alternatives to PagerDuty Operations Cloud. I have been a bit old school, where we used to get paged on our phone numbers. Aside from PagerDuty Operations Cloud, I cannot recall using anything else.
Which other solutions did I evaluate?
Some alternatives to PagerDuty Operations Cloud could be Automation Anywhere, Tray.io, IBM RPA, and a few solutions from Hyland and SAP that also do automation.
What other advice do I have?
While I cannot provide specific pricing details, I can share my perspective as an operations professional. Though we use Jira and initially relied on ServiceNow, we have transitioned more towards Vulcan. We never considered moving away from PagerDuty Operations Cloud. I believe that whatever the cost is, it is beneficial because the IT infrastructure operations industry cannot function without PagerDuty Operations Cloud or a similar product. Furthermore, PagerDuty Operations Cloud has an excellent reputation.
New users are onboarded to ServiceNow or Jira, and they immediately create a PagerDuty Operations Cloud account profile that goes through a verification and approval process by a hierarchy. Once approved, they can set up their numbers and build their profiles to reflect their department, area of expertise, and time zone, allowing them to track incidents outside their shifts while remaining informed about ongoing schedules.
OpenScape is one product that I used before. I worked with Siemens in healthcare IT infrastructure operations, and during that period, we used BMC Remedy integrated with OpenScape, which was back around 2013 to 2016. Back then, our phone numbers were connected to it, but it was not particularly helpful. If you were not in front of your laptop, you received a call, and the automated IVR provided a brief description of the incident logged. You could only acknowledge or resolve the incident without having the option to assign it. OpenScape was what I had used before opting for PagerDuty Operations Cloud at Salesforce starting in 2021, and continuing with PagerDuty Operations Cloud became more widespread at Autodesk in 2022. As I mentioned earlier, some developers have indicated that integrating bots presents a challenge that has been somewhat resolved over time, but that is the only negativity I have heard about PagerDuty Operations Cloud. I rate this product overall a nine out of ten.