It is difficult to send underlying trace files or statuses using PagerDuty. You can set up email alerts, but you cannot build any triggers using those email alerts. There are limitations; you cannot extend it to send alerts to other teams. You can escalate it within the team but not redirect the alert to different teams.
We were exploring ManageEngine ServiceDesk. So, we need a feature where we can, like, when an alert triggers, we should alert the recipient by on-call. So, when an alert is detected, a ticket is generated in the management team, and we want to notify them on-call. Like, this ticket has been generated and stuff. So, I would like to see a similar feature in this solution. This is why we want an alternative to PagerDuty. We want an alternative to PagerDuty. So we are getting on-call notifications using PagerDuty, but now we want to replace PagerDuty with ManageEngine ServiceDesk. So whenever some incident happens in the cloud infrastructure, we get data alerts from cloud security. We want to integrate a service that will provide us with notifications on-call. That this server is down, or this website is down, or this thing is going wrong. Another area of improvement is integration. It cannot be integrated with our upgraded Jira system. That's why we are dropping PagerDuty. We won't continue using it due to integration issues.
It is a very non-customizable product, so you cannot add things like root cause analysis or the classification of incidents based on the area where you are getting more incidents. For example, if you're getting a lot of database issues, that may be an are you want to probe. There aren't any capabilities to integrate with any problem management issues, like repetitive or high impact issues to deep dive and track them in the PagerDuty system. That is, I would like to see integration of problem management with incident management. That would be one nice feature to have.
The user interface could be more intuitive. Initially, when we started using it, we had issues viewing some options because we had information issues in my role as an observer, not the responder. Therefore, I couldn't view buttons like acknowledgements because they were not showing up.
Learn what your peers think about PagerDuty Operations Cloud. Get advice and tips from experienced pros sharing their opinions. Updated: November 2024.
I would like the UI to be more intuitive. I would like to be able to group or color-code the discoveries. When you create a system, you have a listing of all the different configurations. You can list them by teams, but some additional color coding would be helpful. I would break it down by incident controls. In other words, it should be broken down it into response teams and engineering divisions.
Director of engineering at a wellness & fitness company with 51-200 employees
Real User
2022-09-13T19:02:11Z
Sep 13, 2022
The biggest area for improvement with PagerDuty is noise suppression. There have been a handful of incidents through our use of PagerDuty over the years where one incident may lead to 30 to 50 pages because you're monitoring all these different things, and each thing is an individual page. There should be the ability to set up paging tiers and group correlations between some of the different pages. That is something that would be really valuable. We should be able to say this one page may have a group or a tree of effective other pages that may tier off of it. So, if you see those pages independently, go ahead and alarm, but if you see this plus that, don't do that.
Compliance, Security & Testing Manager at a financial services firm with 11-50 employees
Real User
2020-10-08T07:25:00Z
Oct 8, 2020
Because of the way you have to structure the rosters, if an engineer has to go on leave (or something), you can't just go in and reassign/take this person out of all of the different rosters that they're in. You have to go into each of the rosters and take them out. There might be a roster for business hours, after hours rotation, and monitoring deployments. Each time we need to take an engineer out of the pool, e.g., if they're sick or on leave, then we have to go and touch all of those rosters, updating and replacing them. Whereas, if we could just take the person out and have it automatically fill in the rostering, then that would make life a lot easier for managing it. We have an on-call phone number. However, at the moment, it is routed to a static voicemail. We would actually like to be able to have that phone follow whoever is on-call.
The solution's analytics are okay. I don't think the features, at this point, give you a lot of insights. We have actually been trying to get insights from it but it hasn't really given us a lot of extra points to explore. We were looking at the number of alerts to see where many of the alerts were coming from. We never managed to get many insights on this. The solution has not enabled us to go beyond responding to incidents and to start predicting or preventing them. It would help if they simplified the way you try to get insights or information about instances and to improve your situation regarding the groupings of alerts. Even if there are a lot of different functionalities, a lot of prediction abilities in place, it's not really clear what the best practices are for using PagerDuty to get the best out of the platform. The concepts are quite complex, at times, for people to understand. They need a more straightforward way to use the product and get the best out of it. With all the concepts of escalation, services, and the schedule, it gets confusing.
Tier 4 Support Team Leader at a Comms Service Provider
Real User
2020-03-01T06:37:00Z
Mar 1, 2020
There is room for improvement with the time schedule. The way the schedule currently works is you assign all the team members in one schedule and it automatically spreads them around throughout the schedule. Due to that, I need to do extra work to adjust it, due to specific team needs or how I'm staffing my team. It would be better to be able to edit the schedule and place my team members where I want, or at least to have that option in addition to the automatic process. I find myself redoing the schedule often. Every month I need to make another schedule. It's not so bad but it could be improved.
I would like to see them increase the content base and add integrations with different systems, for example, with ZenDesk or Slack; if it could integrate more with those types of systems. We use ZenDesk; I’d like to link this to ZenDesk. I’d like more integration points.
The PagerDuty Operations Cloud is the platform for mission-critical, time-critical operations work in the modern enterprise. Through the power of AI and automation, it detects and diagnoses disruptive events, mobilizes the right team members to respond, and streamlines infrastructure and workflows across your digital operations. The Operations Cloud is essential infrastructure for revolutionizing digital operations to compete and win as a modern digital business.
PagerDuty Features
PagerDuty...
It is difficult to send underlying trace files or statuses using PagerDuty. You can set up email alerts, but you cannot build any triggers using those email alerts. There are limitations; you cannot extend it to send alerts to other teams. You can escalate it within the team but not redirect the alert to different teams.
It’s quite hard to reach the support team.
We were exploring ManageEngine ServiceDesk. So, we need a feature where we can, like, when an alert triggers, we should alert the recipient by on-call. So, when an alert is detected, a ticket is generated in the management team, and we want to notify them on-call. Like, this ticket has been generated and stuff. So, I would like to see a similar feature in this solution. This is why we want an alternative to PagerDuty. We want an alternative to PagerDuty. So we are getting on-call notifications using PagerDuty, but now we want to replace PagerDuty with ManageEngine ServiceDesk. So whenever some incident happens in the cloud infrastructure, we get data alerts from cloud security. We want to integrate a service that will provide us with notifications on-call. That this server is down, or this website is down, or this thing is going wrong. Another area of improvement is integration. It cannot be integrated with our upgraded Jira system. That's why we are dropping PagerDuty. We won't continue using it due to integration issues.
The product can be improved by including out-of-the-box integration with other standard tools used in our fields such as Confluence and Jira.
It is a very non-customizable product, so you cannot add things like root cause analysis or the classification of incidents based on the area where you are getting more incidents. For example, if you're getting a lot of database issues, that may be an are you want to probe. There aren't any capabilities to integrate with any problem management issues, like repetitive or high impact issues to deep dive and track them in the PagerDuty system. That is, I would like to see integration of problem management with incident management. That would be one nice feature to have.
The user interface could be more intuitive. Initially, when we started using it, we had issues viewing some options because we had information issues in my role as an observer, not the responder. Therefore, I couldn't view buttons like acknowledgements because they were not showing up.
I am not a direct end user of PagerDuty. It's hard to consider its shortcomings in that sense.
I would like the UI to be more intuitive. I would like to be able to group or color-code the discoveries. When you create a system, you have a listing of all the different configurations. You can list them by teams, but some additional color coding would be helpful. I would break it down by incident controls. In other words, it should be broken down it into response teams and engineering divisions.
The biggest area for improvement with PagerDuty is noise suppression. There have been a handful of incidents through our use of PagerDuty over the years where one incident may lead to 30 to 50 pages because you're monitoring all these different things, and each thing is an individual page. There should be the ability to set up paging tiers and group correlations between some of the different pages. That is something that would be really valuable. We should be able to say this one page may have a group or a tree of effective other pages that may tier off of it. So, if you see those pages independently, go ahead and alarm, but if you see this plus that, don't do that.
Because of the way you have to structure the rosters, if an engineer has to go on leave (or something), you can't just go in and reassign/take this person out of all of the different rosters that they're in. You have to go into each of the rosters and take them out. There might be a roster for business hours, after hours rotation, and monitoring deployments. Each time we need to take an engineer out of the pool, e.g., if they're sick or on leave, then we have to go and touch all of those rosters, updating and replacing them. Whereas, if we could just take the person out and have it automatically fill in the rostering, then that would make life a lot easier for managing it. We have an on-call phone number. However, at the moment, it is routed to a static voicemail. We would actually like to be able to have that phone follow whoever is on-call.
The solution's analytics are okay. I don't think the features, at this point, give you a lot of insights. We have actually been trying to get insights from it but it hasn't really given us a lot of extra points to explore. We were looking at the number of alerts to see where many of the alerts were coming from. We never managed to get many insights on this. The solution has not enabled us to go beyond responding to incidents and to start predicting or preventing them. It would help if they simplified the way you try to get insights or information about instances and to improve your situation regarding the groupings of alerts. Even if there are a lot of different functionalities, a lot of prediction abilities in place, it's not really clear what the best practices are for using PagerDuty to get the best out of the platform. The concepts are quite complex, at times, for people to understand. They need a more straightforward way to use the product and get the best out of it. With all the concepts of escalation, services, and the schedule, it gets confusing.
There is room for improvement with the time schedule. The way the schedule currently works is you assign all the team members in one schedule and it automatically spreads them around throughout the schedule. Due to that, I need to do extra work to adjust it, due to specific team needs or how I'm staffing my team. It would be better to be able to edit the schedule and place my team members where I want, or at least to have that option in addition to the automatic process. I find myself redoing the schedule often. Every month I need to make another schedule. It's not so bad but it could be improved.
Something that needs to be improved is adding multilingual support.
I would like to see them increase the content base and add integrations with different systems, for example, with ZenDesk or Slack; if it could integrate more with those types of systems. We use ZenDesk; I’d like to link this to ZenDesk. I’d like more integration points.