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

Rootly vs Splunk On-Call comparison

Why PeerSpot?
 

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
11th
Average Rating
8.0
Reviews Sentiment
5.6
Number of Reviews
4
Ranking in other categories
No ranking in other categories
Splunk On-Call
Ranking in IT Alerting and Incident Management
9th
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 September 2026, in the IT Alerting and Incident Management category, the mindshare of Rootly is 2.8%, down from 9.8% compared to the previous year. The mindshare of Splunk On-Call is 3.5%, down from 4.5% compared to the previous year. It is calculated based on PeerSpot user engagement data.
IT Alerting and Incident Management Mindshare Distribution
ProductMindshare (%)
Splunk On-Call3.5%
Rootly2.8%
Other93.7%
IT Alerting and Incident Management
 

Featured Reviews

Luis Vasconcelos - PeerSpot reviewer
System Architect at CI&T
Centralized incident workflows have improved visibility and streamlined communication across teams
Rootly helps me handle those issues by using a predefined template to define roles inside the workflow and utilizing a basic flow, which is very short in its lifecycle. The most powerful feature of Rootly is its visibility; we can create a dashboard and integrate with Slack and Jira, for example, automating many steps in the follow-up process, which helps to centralize all communications around issues. The best features Rootly offers include communication capabilities, particularly the integration with Slack, which stands out for me because it allows for very clean and direct communication with all clients and even with the resolution area. The Slack integration helps my team by creating a specific resolution group and an automation channel inside Slack once an incident is opened in Rootly, ensuring that everyone knows when a new incident arises. It is not just a notification; we create a group where all the relevant people can help solve the issue quickly. The workflow capability of Rootly to create flows is another key feature for our operation, allowing us to establish specific rules for incidents in Jira or manage the metrics we need during the incident lifecycle, effectively automating many manual processes. Rootly has positively impacted my organization, and we have measured its impact by analyzing the number of incidents we handle over a period. 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. Other positive outcomes include time savings and improvements in collaboration; the groups inside Slack enable people to communicate across different areas and work directly with client operations, creating synergy and a strong integration between teams.
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 saving time with manually adding timelines, as they are already built in when timelines are added in Slack through integration."
"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 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."
"Rootly has positively impacted my organization by allowing us to receive the on-call alerts successfully, whereas before Rootly, we had issues missing alerts."
"The big benefit of using Splunk On-Call is that I know I have a high-performance team, but now I can really measure and prove it."
"Its the best solution of its type out there, you should go for it."
"Transmogrifier and automatic solution report gives me a report with the solution and the way to solve issues when an error occurred."
"We are very satisfied with the tool."
"I would recommend VictorOps for global distributed support teams."
"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."
"VictorOps has been good enough for us and it's effective for our needs in case of an on-call escalation process."
"It reduces the communication around CI/CD and production errors in about 90% of the cases and made our support tasks much easier."
 

Cons

"Regarding Rootly's AI capabilities, we had one incident when we lost alerting generally because Rootly crashed, and we did not like it."
"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."
"There are a few areas where Rootly can be improved."
"Another example is that you cannot check the incidents created in VictorOps from the previous Friday."
"A few things I would improve in Splunk On-Call. Honestly, the reporting and analysis side feels a bit weak."
"Should have more YouTube webinars."
"At that stage, all our needs are fulfilled, but at the beginning, we had some feature requests and they were deployed during their roadmap."
"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."
"One area for improvement would be enhancing the mobile app experience."
"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."
"There could be improvements with communicating an incident or alert."
 

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.
914,394 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Performing Arts
27%
Comms Service Provider
7%
Financial Services Firm
7%
Transportation Company
7%
Retailer
15%
Construction Company
10%
Outsourcing Company
10%
Financial Services Firm
9%
 

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?
There are a few areas where Rootly can be improved. More customization options for postmortem templates and reports would be helpful. Enhancing search functionality to make it easier to locate hist...
What is your primary use case for Rootly?
I use Rootly every day to manage the end-to-end incident lifecycle. When a critical incident is reported, I create or join an incident on Rootly, assign the appropriate severity, and engage the req...
What is your experience regarding pricing and costs for VictorOps?
I would say it is very affordable. I have compared Splunk On-Call internally with our own homemade solution. I have also compared it with other vendors such as PagerDuty, and it is really affordable.
What needs improvement with VictorOps?
I would say a little bit of the user experience and the user interface of Splunk On-Call can be improved. I have already started to gather metrics from the tool and started to analyze that. I would...
What is your primary use case for VictorOps?
I am currently working with Splunk Cloud, but I could review Splunk Enterprise as well because it is fundamentally the same product but with hosting being on-premises instead. Splunk Enterprise, Sp...
 

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: September 2026.
914,394 professionals have used our research since 2012.