We performed a comparison between IBM WebSphere BPMS and PagerDuty Operations Cloud based on real PeerSpot user reviews.
Find out in this report how the two Process Automation solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI."This product is flexible in its ability to integrate processes and it can be extended and integrated with other software."
"The UI capabilities of the solution are great. The speed of delivery is good."
"We like the feature in which we can trace back instances."
"The most valuable feature of PagerDuty is its integration with other tools, such as Amazon AWS, to receive notifications or create automatic instances."
"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."
"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."
"PagerDuty is very stable and very reliable."
"The product easily integrates with other solutions."
"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."
"Alert deduplication and noise reduction for alerts are the major features that I found useful."
"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."
"Sometimes there are tasks that failed without any reason."
"The solution lacks acceptable stability."
"The user interface could be improved, and although integration opportunities are good, they could be improved further."
"PagerDuty's webhooks need some improvement."
"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."
"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."
"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."
"PagerDuty should be integrated with other tools, so it can import the IT roster automatically. Our other rules continue to work once they're configured, but the roster must be added manually."
"I would like to see more content in the notification messages; although, that might be a configuration on our end."
"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."
"The On-Call Teams feature could be better in terms of levels of conditions related to which team or member should get the responsibility of handling a matter or incident."
Earn 20 points
IBM WebSphere BPMS is ranked 32nd in Process Automation while PagerDuty Operations Cloud is ranked 11th in Process Automation with 35 reviews. IBM WebSphere BPMS is rated 6.6, while PagerDuty Operations Cloud is rated 8.8. The top reviewer of IBM WebSphere BPMS writes "Standardizes and automates business processes for efficiency ". On the other hand, the top reviewer of PagerDuty Operations Cloud writes "Effectively generates alerts for incidents, making it suitable for 24/7 monitoring of infrastructure". IBM WebSphere BPMS is most compared with , whereas PagerDuty Operations Cloud is most compared with Opsgenie, ServiceNow, JIRA Service Management, Splunk On-Call and Everbridge IT Alerting. See our IBM WebSphere BPMS vs. PagerDuty Operations Cloud report.
See our list of best Process Automation vendors.
We monitor all Process Automation reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.