No more typing reviews! Try our Samantha, our new voice AI agent.

Rootly vs Splunk On-Call comparison

 

Comparison Buyer's Guide

Executive Summary

Review summaries and opinions

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Categories and Ranking

Rootly
Ranking in IT Alerting and Incident Management
5th
Average Rating
8.0
Reviews Sentiment
5.6
Number of Reviews
5
Ranking in other categories
No ranking in other categories
Splunk On-Call
Ranking in IT Alerting and Incident Management
10th
Average Rating
8.6
Reviews Sentiment
7.2
Number of Reviews
13
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of August 2026, in the IT Alerting and Incident Management category, the mindshare of Rootly is 3.1%, down from 10.0% compared to the previous year. The mindshare of Splunk On-Call is 3.4%, down from 4.4% compared to the previous year. It is calculated based on PeerSpot user engagement data.
IT Alerting and Incident Management Mindshare Distribution
ProductMindshare (%)
Rootly3.1%
Splunk On-Call3.4%
Other93.5%
IT Alerting and Incident Management
 

Featured Reviews

HJ
Manager at teshama
Seamless Slack incidents have standardized my workflows and have streamlined post mortems
Slack-based workflow in Rootly helps my team during incidents by simplifying incident management and workflows, easing writing post-mortems, supporting planned maintenance, and offering valuable team support for migration and training. It's streamlining our incident management process overall, and having everything automated and flexible is extremely valuable through automations. The best features Rootly offers are all-in-one incident management and an intuitive user-friendly GUI. I find the user interface highly intuitive because it's very easy to customize and navigate, even for new users, hence making the learning curve very comfortable and smooth. Rootly is very valuable, especially because it's very cost-effective. It's also very easy to use, and it has a very proactive and supportive customer support team. I have seen a return on investment as Rootly has made interactions smoother and more efficient. The speed of Rootly makes my work more productive.
Ramani Happy - PeerSpot reviewer
Dev Ops Engineer at Data Elicit Solutions Pvt. Ltd.
Streamlined incident response has reduced downtime and improved on-call collaboration
A few things I would improve in Splunk On-Call. Honestly, the reporting and analysis side feels a bit weak. If I want to deep dive into the on-call load, including MTTD and MTTR rates, I kind of have to export data and build my own dashboard, which is not as out-of-the-box as I would prefer. The UI has improved, but it still feels a little chunky in certain areas, particularly when managing schedules. When I have a lot of teams, it can get messy. Additionally, the pricing model is per user, which starts to get expensive as the team scales.

Quotes from Members

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Pros

"Rootly has positively impacted my organization by allowing us to receive the on-call alerts successfully, whereas before Rootly, we had issues missing alerts."
"With the strategic approach of putting everyone in a Slack group to resolve incidents, we have reduced the percentage of incidents created in a month by thirty percent during the first three months of using Rootly."
"Rootly has positively impacted my organization by saving time with manually adding timelines, as they are already built in when timelines are added in Slack through integration."
"Rootly is very valuable, especially because it's very cost-effective, very easy to use, and it has a very proactive and supportive customer support team."
"Rootly has positively impacted our organization because, in comparison to ObsGenie, the tool we used before Rootly, it is much more user-friendly, including the user interface and the whole approach to alerting and routing these alerts."
"Transmogrifier and automatic solution report gives me a report with the solution and the way to solve issues when an error occurred."
"VictorOps has been good enough for us and it's effective for our needs in case of an on-call escalation process."
"I would recommend VictorOps for global distributed support teams."
"The alert calling feature is the best because notifications are delivered via phone messages."
"Splunk On-Call has helped my organization to improve response times, reduce missed alerts, and coordinate teams more efficiently during incidents."
"VictorOps has decreased the meantime to acknowledge an incident management process, our developers can be on-call faster when we are using this solution, and we can fix our incidents much quicker."
"My VP of Operations is ecstatic about the VictorOps product."
"The most valuable feature of the solution is helpdesk escalation."
 

Cons

"Regarding Rootly's AI capabilities, we had one incident when we lost alerting generally because Rootly crashed, and we did not like it."
"There are a few areas where Rootly can be improved."
"The integration process could be easier, perhaps with the addition of AI to facilitate smoother integrations with other applications, especially since those who manage integrations often need technical knowledge about web services and single sign-on processes, which can be challenging for non-technical users."
"Rootly can be improved as it's slightly buggy for new features."
"Should have more YouTube webinars."
"There could be improvements with communicating an incident or alert."
"We chose to move away from the HP product as far as our monitoring goes and dealing with system-generated alerts, simply because it took too much time and effort to manage the APM platform."
"Another example is that you cannot check the incidents created in VictorOps from the previous Friday."
"I would say a little bit of the user experience and the user interface of Splunk On-Call can be improved."
"The only feature that we are currently waiting on right now is really kind of an annoyance factor: when we get on the timeline on the main dashboard, there’s an ACK All button."
"Many years ago, when VictorOps was a standalone company, when it was not part of Splunk, their support was more dedicated for us."
"The third-party configuration tool could be easier to use."
 

Pricing and Cost Advice

Information not available
"The price of the solution could be less expensive."
report
Use our free recommendation engine to learn which IT Alerting and Incident Management solutions are best for your needs.
909,153 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Performing Arts
28%
Comms Service Provider
7%
Financial Services Firm
7%
Transportation Company
7%
Construction Company
12%
Financial Services Firm
10%
Performing Arts
10%
Outsourcing Company
6%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
No data available
By reviewers
Company SizeCount
Small Business1
Midsize Enterprise1
Large Enterprise10
 

Questions from the Community

What is your experience regarding pricing and costs for Rootly?
Regarding my experience with pricing, setup cost, and licensing, we got a license for one year. Generally, it is great and the price is great, and that is the reason we chose Rootly. The only thing...
What needs improvement with Rootly?
Regarding improvements for Rootly, first of all, it would be great to make comfortable maintenance mode, as it does not let me silence alerting comfortably. This is one of a very small list of poin...
What is your primary use case for Rootly?
Rootly is our central system for on-call and alert management. We route alerts from Alertmanager to Rootly, and after that, we route alerts from Rootly to different teams that are in charge of the ...
What is your experience regarding pricing and costs for VictorOps?
The pricing aspect is per-user licensing, which is standard for this category, making it competitive compared to PagerDuty. In the past, we used PagerDuty, but it is not cheap once you start adding...
What needs improvement with VictorOps?
A few things I would improve in Splunk On-Call. Honestly, the reporting and analysis side feels a bit weak. If I want to deep dive into the on-call load, including MTTD and MTTR rates, I kind of ha...
What is your primary use case for VictorOps?
I have been using Splunk On-Call for nearly about two years. Our main use is incident alerting and on-call scheduling for our engineering and DevOps team. Basically, whenever something goes down, a...
 

Comparisons

 

Also Known As

No data available
VictorOps
 

Overview

 

Sample Customers

* **Atlassian** * **Cisco** * **Databricks** * **DigitalOcean** * **Google Cloud** * **IBM** * **JetBlue** * **LinkedIn** * **Lyft** * **Microsoft** * **MongoDB** * **Netflix** * **Pinterest** * **Qualcomm** * **Red Hat** * **Salesforce** * **Spotify** * **Square** * **T-Mobile** * **Twitter** * **Uber** * **VMware** * **WeWork** * **Workday** * **Xerox** * **Zoom**
NVIDIA, Cisco, NBC, Rackspace, Intuit, DirectTV, NASCAR, Arrow Electronics, Alliance Health, NetApp, Edmunds, New York Times, Return Path, Sony Playstation, CA Technologies, Sphero, Symantic, HBO, Weatherford, Blackboard, Epic Games
Find out what your peers are saying about Rootly vs. Splunk On-Call and other solutions. Updated: June 2026.
909,153 professionals have used our research since 2012.