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

Rootly vs Splunk ITSI (IT Service Intelligence) 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
4
Ranking in other categories
No ranking in other categories
Splunk ITSI (IT Service Int...
Ranking in IT Alerting and Incident Management
4th
Average Rating
8.4
Reviews Sentiment
6.6
Number of Reviews
64
Ranking in other categories
Application Performance Monitoring (APM) and Observability (10th)
 

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 ITSI (IT Service Intelligence) is 2.0%, down from 2.4% compared to the previous year. It is calculated based on PeerSpot user engagement data.
IT Alerting and Incident Management Mindshare Distribution
ProductMindshare (%)
Splunk ITSI (IT Service Intelligence)2.0%
Rootly3.1%
Other94.9%
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.
DS
Senior Consultant at a consultancy with 10,001+ employees
Service health has been monitored and visual insights support proactive telecom operations
The installation process is the first aspect I dislike about Splunk ITSI (IT Service Intelligence). If you do not configure it correctly, you will encounter issues in the search head. Because we use a distributed environment where each component has its own specific roles, installation is critical and requires careful attention. Splunk ITSI (IT Service Intelligence) is built with many applications. It is a compressed file, and when you extract the Splunk ITSI (IT Service Intelligence) app, you receive approximately 19 apps. Some applications, add-ons, and packages must be installed on specific components. If you do not configure an application correctly, it will not work. Sometimes we encounter issues during installation because of this complexity. I believe the installation process should be more uniform, meaning it could be deployed across all components to avoid post-installation issues. Sometimes after installation, you receive errors, and users cannot access Splunk ITSI (IT Service Intelligence). We have experienced this type of issue due to installation errors. I believe there is currently room for improvement regarding scalability. When we create Glass Tables containing many searches, the Glass Tables sometimes fail due to memory constraints, and we receive error pages. Splunk ITSI (IT Service Intelligence) should have a lightweight version to address these concerns. I would rate current scalability as medium.

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 my organization by allowing us to receive the on-call alerts successfully, whereas before Rootly, we had issues missing alerts."
"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."
"One of the excellent features is the service analyzer, which is truly impressive."
"Splunk's intuitive interface and scalability make it accessible to non-technical users, and its capacity to monitor every millisecond of data across multiple applications is truly impressive."
"The service analyzer view and automatic creation of incidents are valuable."
"Splunk ITSI can be easily integrated with the incident management platform. You can automate workflows and certain actions can be taken."
"Splunk ITSI helps us secure our environment by allowing us to create automatons that run when alerts are triggered."
"The most valuable features are the agility, being able to ingest many data sources with no limitation on capacity."
"We have a lot of teams using Splunk and they would be blind without it."
"What I like the most is the event correlations. It's a file structure, and ITSI has a correlation layer where you can normalize the events from different sources. Once these events are normalized, you set up rules to aggregate them into different or the same attributes. After the rules are defined, you can automate the process to solve the issue automatically."
 

Cons

"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."
"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."
"There should be entity conflict resolution, specifically regarding duplicate entities. There should be case sensitivity for various keys amongst entities, specifically host names. We need IT metrics-based indexes and more content packs. I know they are coming out with these features"
"It could be a little easier to use with the thresholding. We've struggled a little bit with thresholding."
"Integration is the most critical area to improve in Splunk IT Service Intelligence (ITSI). It wasn't a great experience because you had to do a little back and forth to integrate the solution."
"It would be advantageous to enhance the dashboard by incorporating sections for monitoring, service health, and a filter for the KPIs."
"We also faced challenges relating to UI development."
"It would be good if an interface was included in the next release."
"Occasionally, we have faced some slowness, which we reported to Splunk, and those issues were promptly resolved."
"They should make it easier to use. Many people are new to it. It is hard and has a steep learning curve."
 

Pricing and Cost Advice

Information not available
"Splunk pricing is high."
"I wouldn't say there's been an issue with the solution's pricing because we went through the AWS marketplace and negotiated directly with Splunk."
"Splunk ITSI is expensive."
"The pricing of Splunk is a bit high."
"The cost of the modules is a bit high for non-global companies, making it difficult for them to afford Splunk ITSI."
"Splunk ITSI is expensive; however, with the appropriate use case, it justifies the cost."
"Splunk ITSI is expensive."
"Splunk ITSI is expensive compared to other tools."
report
Use our free recommendation engine to learn which IT Alerting and Incident Management solutions are best for your needs.
909,725 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%
Financial Services Firm
16%
Manufacturing Company
10%
Outsourcing Company
9%
Construction Company
7%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
No data available
By reviewers
Company SizeCount
Small Business17
Midsize Enterprise8
Large Enterprise46
 

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 Splunk ITSI (IT Service Intelligence)?
From a pricing perspective, it is not that bad because we get it from a distributor and do not purchase it directly from Splunk. We get it from a distributor who gives the pricing to a partner and ...
What needs improvement with Splunk ITSI (IT Service Intelligence)?
In terms of improvements for Splunk ITSI (IT Service Intelligence), I would suggest adding more out-of-the-box plugins and adapters, especially as there is a high demand for observability and dashb...
What is your primary use case for Splunk ITSI (IT Service Intelligence)?
I use Splunk ITSI (IT Service Intelligence) as a manager of the managers, a tool sitting on top of all the other observability tools. It gets the alerts feed from all the sources such as Splunk Ent...
 

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**
TransUnion, Cox Automotive, Carnival Cruises, Leidos, Econocom, National Ignition Factory, Entrust Datacard, Molina Healthcare, United States Census Bureau
Find out what your peers are saying about Rootly vs. Splunk ITSI (IT Service Intelligence) and other solutions. Updated: August 2026.
909,725 professionals have used our research since 2012.