We performed a comparison between PagerDuty Operations Cloud and xMatters based on real PeerSpot user reviews.
Find out in this report how the two IT Alerting and Incident Management solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI.
"It has scaled well for us."
"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."
"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."
"PagerDuty's notification process is the most valuable feature."
"The product has valuable on-call scheduling, escalation, and incident workflow management features."
"The inbound integrations that PagerDuty provides with most of the DevOps tools are valuable."
"PagerDuty is very stable and very reliable."
"Notification is the most valuable feature."
"The UI: It is easily navigable."
"It has improved our time to respond. Prior to the use of xMatters, it might take hours or even a day to get someone involved on a problem. Now, it's down to minutes."
"For us, their biggest feature is event alerting and the retention of those events. This way, if something goes wrong, we can provide a report of everything that was sent out and everything that was captured."
"Simple features create flow sets and build APIs for integrations."
"We saw the value by being able to import everyone's schedule into one common central repository and have one tool for all the operational teams, or any team for that matter. It gave us the technology to find out who is on call. The incident management of xMatters' integration was another key aspect, where we could say, "You can configure this when a high ticket fires.""
"We haven't evaluated any product recently, but from what I can tell, looking around online, what xMatters has that others don't have are the custom forms. That's the big differentiator at the moment because that's something that we heavily use."
"One of the things that really attracted me is in workflows, you can write your own custom steps in JavaScript. You are not restricted to the steps that they provide. If you can write it in JavaScript, you can pretty much do anything. It gives me flexibility in ways that other platforms don't. For example, the online dashboard system we use is not a widely used one, but they have an API. So, I'm able to write the JavaScript steps to do things like check if a system's in the maintenance window or create an instant on the dashboard or change the status of an instant. I'm not dependent on the dashboard provider or xMatters creating steps for me."
"It has been easy to use and very reliable."
"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."
"It’s quite hard to reach the support team."
"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."
"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."
"They could include incident merging and alert grouping features in the product."
"PagerDuty's webhooks need some improvement."
"PagerDuty can improve the integration with Terraform."
"While they do have an extensive library of integrations, sometimes those integrations or custom integrations, require a more technical level of expertise in products outside of xMatters, such as Java."
"I would like some minor UI changes. I believe I filed some enhancement requests with xMatters. For example, in one area, they have some way for you to look at a particular functionality with different sets of reporting UI. However, that same reporting UI is not yet available with some other functionalities. Essentially, in their existing functionality, the xMatters application does an excellent job, but in other functionalities within their UI, they don't have that. On the back-end, they are related. Instead of one click where you can see everything, right now you need to go to different areas to access similar information. It would be nice to have everything in one place. While they have an excellent element A, I am hoping that they could just simply make that feature also available in their element B."
"The data validation and verification need to be enhanced so that when data is changed, it reviews it in an automated manner and catches all of the anomalies."
"Integrations seem to be the most difficult part. Once setup though, they work well."
"I would like to see some more user templates. There are roles — administrator, user, etc. — but it would be nice to create a user template that restricted what people assigned that role could do."
"As an agent, as someone who is on call, I can mark an absence time and I can optionally put somebody in my place, but once you've done that, you can't edit it. You have to delete it and create a new absence, which is annoying, but it's not a massive issue. It's a minor annoyance. That's probably about the only thing I can come up with because I absolutely love the product. It's met our needs so well."
"I've asked for the ability to have tags on groups, and for dynamic lists, meaning the ability to pull data from another location and use it in xMatters dynamically. Right now, for example, if I have a form and want to populate a list, it's a manual process. I have to copy and paste the list items."
"On-call management scheduling is difficult."
PagerDuty Operations Cloud is ranked 1st in IT Alerting and Incident Management with 35 reviews while xMatters is ranked 3rd in IT Alerting and Incident Management with 31 reviews. PagerDuty Operations Cloud is rated 8.8, while xMatters is rated 8.8. The top reviewer of PagerDuty Operations Cloud writes "Effectively generates alerts for incidents, making it suitable for 24/7 monitoring of infrastructure". On the other hand, the top reviewer of xMatters writes "Enabled us to meet our "lights out" goal and repurpose staff to do work of greater value". PagerDuty Operations Cloud is most compared with Opsgenie, ServiceNow, JIRA Service Management, Splunk On-Call and BigPanda, whereas xMatters is most compared with Opsgenie, ServiceNow, Everbridge IT Alerting, OnSolve Platform for Critical Event Management and Splunk On-Call. See our PagerDuty Operations Cloud vs. xMatters report.
See our list of best IT Alerting and Incident Management vendors.
We monitor all IT Alerting and Incident Management 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.
