"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."
"The most valuable feature is definitely the flexibility of the schedule. The mobile app is quite also good for what we do: for receiving alerts, acknowledging, assigning, adding new responders. It has rich features for our needs."
"It reduces the amount of white noise. If something comes through, then it will alert somebody. However, if it's a bit of white noise that comes through at night, then it gets dealt with the next day. Everything is visible to everybody. It's not just a single person getting an SMS, then going, "Oh, I'm not going to worry about that." The visibility to everybody on the team is one of the great things about it because it reduces the white noise."
"That automation is the critical aspect of xMatters. Without those workflows, then we would have a system that maintains an on-call schedule in Excel. So xMatters provides the notification workflow and ensures you're notifying the right person at the right time."
"The automatic logging that's built into xMatters, especially the timeline of events, is very helpful because we can figure out why a particular person got a call... Having that level of detail built-in makes it really easy for me or the managers to prove that's what happened, and we can self-serve that information. It gives people the autonomy to know why they got a call."
"Workflows and messaging are most valuable. Workflows are very useful. They are important for consolidating information or stopping duplication from happening. We put all the information into xMatters and then the workflow will push the same information in the correct format directly through to other applications that our end users frequently use, such as Slack, email, and Workplace."
"The Flow Designer is quite valuable, as you can set up integrations and flows without necessarily needing to know about code."
"Probably the most important one is that it persists in attempting to contact to someone until someone is engaged on the event."
"The automated callouts, without a doubt, are most valuable. They have been a huge gain for our company. Previous to xMatters, there was no real management of the on-call resources or rotas. So, having that centralized and automated has been a huge gain."
"It reduces the mean time to restore a service. Before, it would probably take an hour to get everybody settled down. With the integrations right now, if somebody flags a major incident, then everyone is on a call in the next 15 minutes."
"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."
"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."
"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."
"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... 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."
"What I would like it to do is tell me anytime there is a P1 incident, except when the ticket is assigned to this team or when this word is in the summary, but there is no exclusion option. I have been complaining about this for a couple years. At one point, we created a ticket for this with the developers to review. I assume that once enough people complain about it, they will bump it up in priority to work on. However, if not enough people think it is an issue, then they prioritize their work and work on other features and functionality. However, this is something that has been challenging for us because we have needed to find ways to work around it or just deal with it. So, I would love to see an exclusion option."
"We would like to see a greater variety of integrations with ServiceNow. It works fine as it is, but an enhancement would be the ability to interact with the major incident module in ServiceNow... The way our major incident process works, when an incident is elevated from a P1 to a major incident, that is an extra flag in ServiceNow. It would be awesome to have xMatters get notification when something goes from a P1 to a major and then have it go through a different workflow, rather than our regular P1."
"The user interface could be more intuitive. Once you know what you're doing, you're fine. However, if you don't know where to start then it can be a bit difficult to figure out how to make it work and how it will function together with different tools in the Flow Designer."
"The only thing that has caught us out a little bit is that on certain screens, you don't have the same admin options. There should be more consistency with the admin options because not all screens provide you with the same options. As an administrator, it feels like they should always be there. For example, on some screens, there is an Export button that provides fantastic, detail-rich exports, which obviously are very handy because then you can, as an administrator, do your administration, and extract what has been done to share with or prove to others. However, the Export button is not always present, and on the screens where it isn't, you miss it. You're like, "Oh, where's the Export button?", which can be quite problematic. There should be more consistency in the UI in terms of available options for anything that is referenced data or configurable. If you can put it in, there should be a way to run an export function to essentially pull it out. That's the only improvement that I can really think of."
"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."
"One of the main reasons why we don't use xMatters for monitoring and alerting is that it doesn't use the rota to call the person who's on-call. It doesn't look up the rota to find out who's on-call and then contacts that person directly. I am not sure if this has changed now, but the last time we checked, this functionality wasn't there. This is one of the main improvements. We're happy with the rest of it."
"It took me awhile to get used to whatever was available in the interface. The interface from two years ago was a bit more confusing when looking at where you should go"
"An additional knowledge-sharing program could be helpful and part of the demo workshops (right now, these only provide partial information)."
Earn 20 points
PagerDuty is an agile incident management solution that integrates with ITOps and DevOps monitoring stacks to improve operational reliability and agility. From enriching and aggregating events to correlating them into actionable alerts, PagerDuty streamlines the incident management lifecycle by reducing noise and resolution times. With hundreds of native integrations with operations tools, automated scheduling, advance reporting and guaranteed availability, PagerDuty is trusted by over 7,000 organizations globally to increase business and employee efficiency. The company is headquartered in San Francisco and backed by leading venture capital firms Andreessen Horowitz, Bessemer Venture Partners, Baseline Ventures, Ignition Partners and others. To try PagerDuty for free, or to get more information, visit www.pagerduty.com.
xMatters, an Everbridge company, is a service reliability platform that helps DevOps, SREs, and operations teams rapidly deliver products at scale by automating workflows and ensuring infrastructure and applications are always working. The xMatters code-free workflow builder, adaptive approach to incident management, and real-time performance analytics all support a single goal: deliver customer happiness.
To learn more, request a demo.
Sign up now
PagerDuty is ranked 2nd in IT Alerting and Incident Management with 3 reviews while xMatters IT Management is ranked 1st in IT Alerting and Incident Management with 14 reviews. PagerDuty is rated 8.4, while xMatters IT Management is rated 9.2. The top reviewer of PagerDuty writes "Reduces white noise, which has reduced engineer fatigue". On the other hand, the top reviewer of xMatters IT Management writes "Gave us the ability to validate whether messages were going out". PagerDuty is most compared with ServiceNow, Opsgenie, Everbridge IT Alerting, JIRA Service Management and BigPanda, whereas xMatters IT Management is most compared with Everbridge IT Alerting, Opsgenie, ServiceNow, VictorOps and Clarity SM. See our PagerDuty vs. xMatters IT Management 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.