We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
"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."
"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.""
"It reduces the amount of oversight required, and consequently, the amount of time to assign and get a response on a ticket."
"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."
"xMatters is helpful for getting the right on-call resources. That is a key factor. It is also very user-friendly, and just a little documentation helps you to understand things such as how on-calls are configured, how groups are configured, and how users update their on-call devices."
"The Flow Designer is quite valuable, as you can set up integrations and flows without necessarily needing to know about code."
"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 main thing that we like about BigPanda is the user interface."
"BigPanda integrates well with other solutions, such as WatchGuard,"
"Alert aggregation was the primary requirement. BigPanda pulls all this together into a single UI for us, allowing us to see related alerts grouped together into an incident, and enables us to easily create a JIRA ticket and Slack channel to manage an issue."
"We have also made extensive use of the outbound integrations to ticketing systems (JIRA) and collaboration tools (Slack). The main driver for us has been getting all alerting into a single UI and enabling us to streamline our incident management process."
"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."
"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."
"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."
"If you want to alter a custom field, you can do so via import/export. But you can't have an unlimited number of custom fields, so in a large environment with a lot of teams, team provisioning becomes more difficult."
"Beyond the typical grouping, xMatters has what is referred to as dynamic teams. Dynamic teams are criteria for setting up and targeting a group of people that meet specific criteria. The bad thing about this setup is that you cannot alter those criteria through the typical xMatters import/export process. The attributes that create the criteria for dynamic teams can only be altered via the Web UI. So, if you want to create a new dynamic team in a mature xMatters environment (one that is already populated with hundreds of users), and you want to add, say, 100 users to that dynamic team, you have to do it manually."
"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"
"When you are not using the conference bridge from xMatters and you are using an external one, it is a little bit hard to get the person whom xMatters calls to jump directly to the external bridge. They need to hang up the phone and then get to the email to get the URL so that they can jump on the bridge. There is no direct connection from xMatters to that external bridge, but I understand that part of the business."
"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."
"The cost of this product is too high compared to New Relic."
"The solution could improve by having better integration."
"Our infrastructure is quite large - tens of thousands of servers, often with 30-plus checks running on each host with one minute intervals. This generates a lot of data often in bursts (when we have a large scale failure). This has caused some delay in the ingestion pipeline."
"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 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."
"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."
"I don't make the decisions on the cost aspect. We haven't had any complaints. I think it has a reasonable price."
"There's a significant difference between a full license, which allows people to respond to and acknowledge receipt of messages, and a more scaled-down license, which just allows people to see the notification. So we need to evaluate what license they need when onboarding new users because the full license is significantly more expensive."
"We're currently per license. We're paying around $44,000 per year for 80 full users and 300 standard users. For a new implementation, we also need to pay for an expert."
"It feels like good value in the sense that the service is excellent. The people above me who look at such things have renewed it a couple of times, and I think they would have thought whether it was good value, whether it was wildly overpriced, or whether there were better and cheaper alternatives. So, from that perspective, the pricing is fair and proper."
"This is a subscription-based, SaaS solution."
"I am not really privy to how much my client is paying for this service. They just tell me the number of licenses that they have. Every time that I say, "I need extra licenses to make sure that all Level 1 and 2s have their own xMatters account," they keep telling me that it is too expensive. If the only purpose is to call people, it doesn't justify the cost of paying more than the number of licenses that they already have."
"The pricing is tiered so we took that into account. If we were to license 10 or 20 people, that would be a certain price. And if we were to license 50 or 100, there would be a little bit of discounting. But the per-user license was right in line with what we were expecting."
"It is worth the cost. You need to know the number of users that are going to use it, which is usually pretty easy to calculate. It's on a per-user license."
"We pay $200,000 USD per year."
"They were great to work with on pricing/licensing. Given we are a high-growth company, we needed a flexible site license."
"The cost is quite high. But if you want to get a full-featured application and you have a big team..."
"If we wanted phone calls or additional SMSs, we would have to pitch up for those. They give us so many per month per user, then we have to pay extra if it goes over that."
"If you add more people, then you have to pay more, which is always a thing with the SaaS solutions."
Earn 20 points
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.
BigPanda Autonomous Operations platform helps IT Ops, NOC and DevOps teams detect, investigate, and resolve IT incidents faster and more easily than ever before. Powered by Open Box Machine Learning, BigPanda correlates IT noise into insights, automates incident management, and unifies fragmented IT operations. Customers such as Intel, TiVO, Turner Broadcasting and Workday rely on BigPanda to reduce their operating costs, improve service availability and performance, and de-risk and accelerate their digital transformation initiatives. Founded in 2012, BigPanda is backed by top-tier investors including Sequoia Capital, Mayfield, and Battery Ventures. Visit www.bigpanda.io for more information.
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.
Sign up now
BigPanda is ranked 4th in IT Alerting and Incident Management with 3 reviews while PagerDuty is ranked 1st in IT Alerting and Incident Management with 3 reviews. BigPanda is rated 8.6, while PagerDuty is rated 8.4. The top reviewer of BigPanda writes "Alert aggregation and the correlation platform are extremely useful, streamlining our incident management". On the other hand, the top reviewer of PagerDuty writes "Reduces white noise, which has reduced engineer fatigue". BigPanda is most compared with Moogsoft, Zabbix, IBM Tivoli NetCool OMNIbus, Splunk and Datadog, whereas PagerDuty is most compared with ServiceNow, Opsgenie, Everbridge IT Alerting, Splunk and Moogsoft. See our BigPanda vs. PagerDuty 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.