We performed a comparison between Splunk On-Call 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."The flexible schedule is the most valuable feature. It was very easy to set out a rotation."
"Transmogrifier and automatic solution report gives me a report with the solution and the way to solve issues when an error occurred."
"The alert calling feature is the best because notifications are delivered via phone messages."
"The most valuable feature of the solution is helpdesk escalation."
"VictorOps has been good enough for us and it's effective for our needs in case of an on-call escalation process."
"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 most valuable features are the ability to have groups and then have an on-call rotation in the groups. Outlook lacks both these features. Outlook gives you the ability to contact an individual or groups, but you can't contact them based on an on-call rotation, and you can't have built-in timing escalations inside of that. xMatters gives you the ability to do that, which is important when you have 50 or so people in the team, but you only want to contact the person who is on-call. You don't create any unnecessary noise. xMatters allows you to page the right person who is on-call versus just creating excessive noise."
"We use xMatters for alarming infrastructure outages and failures of batch jobs (post-processing)."
"The Flow Designer is quite valuable, as you can set up integrations and flows without necessarily needing to know about code."
"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."
"For our organization, sending notifications out via subscriptions for outages."
"Probably the most important one is that it persists in attempting to contact to someone until someone is engaged on the event."
"We're able to point all of our alerting tools at xMatters and have it route alerts to the right people at the right time. We're able to generate major instant notifications for product outages, get all of our people on the bridge at the same time, and include information from our monitoring tools with that. So everyone is speaking the same language and seeing the same information. We're able to route those notifications not only to people, but also to other tools like Slack channels, where everyone can get in and collaborate."
"The third-party configuration tool could be easier to use."
"At that stage, all our needs are fulfilled, but at the beginning, we had some feature requests and they were deployed during their roadmap."
"There could be improvements with communicating an incident or alert."
"Should have more YouTube webinars."
"The solution can be improved by including a wider list of permissions."
"The REST API is still missing some important functionality, which we require."
"We have to create an Excel sheet for onboarding users and then upload it. But if an employee resigns, we don't have any checkpoints to validate whether the user is still active or not. We have to do that manually every week: Check who has left the organization, and do a cross-check, whether this person had any licenses or signed in to xMatters."
"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."
"On-call management scheduling is difficult."
"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."
"They could make the product more customizable."
"They recently released an incident module that allows users, or at least teams, to track major incidents and other things, and you can send out communication via that one webpage. You can engage on-call teams and communicate to stakeholders as well, but one thing that is missing there is a group chat. If there is a group chat on the same webpage that all of the support teams could use, it would be a one-stop shop that all of the major incident managers would use as their product to manage a major incident. Without that, at the moment, they are mainly referring to teams and then adding data into xMatters as and when they can."
"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."
Splunk On-Call is ranked 8th in IT Alerting and Incident Management with 10 reviews while xMatters is ranked 3rd in IT Alerting and Incident Management with 31 reviews. Splunk On-Call is rated 8.6, while xMatters is rated 8.8. The top reviewer of Splunk On-Call writes "Allows us to create flexible schedules for on-call rotations". On the other hand, the top reviewer of xMatters writes "A versatile solution with excellent logging capabilities that reduced our time to resolve ". Splunk On-Call is most compared with PagerDuty Operations Cloud, Opsgenie, New Relic, Everbridge IT Alerting and JIRA Service Management, whereas xMatters is most compared with PagerDuty Operations Cloud, Opsgenie, ServiceNow and Everbridge IT Alerting. See our Splunk On-Call 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.
