Try our new research platform with insights from 80,000+ expert users

Loom Systems vs Splunk Observability Cloud comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Dec 28, 2025

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

Loom Systems
Ranking in IT Infrastructure Monitoring
60th
Average Rating
8.0
Reviews Sentiment
6.9
Number of Reviews
4
Ranking in other categories
Anomaly Detection Tools (4th)
Splunk Observability Cloud
Ranking in IT Infrastructure Monitoring
7th
Average Rating
8.2
Reviews Sentiment
7.0
Number of Reviews
75
Ranking in other categories
Application Performance Monitoring (APM) and Observability (8th), Network Monitoring Software (6th), Cloud Monitoring Software (6th), Container Management (6th), Digital Experience Monitoring (DEM) (2nd)
 

Mindshare comparison

As of January 2026, in the IT Infrastructure Monitoring category, the mindshare of Loom Systems is 0.6%, up from 0.2% compared to the previous year. The mindshare of Splunk Observability Cloud is 2.0%, up from 1.2% compared to the previous year. It is calculated based on PeerSpot user engagement data.
IT Infrastructure Monitoring Market Share Distribution
ProductMarket Share (%)
Splunk Observability Cloud2.0%
Loom Systems0.6%
Other97.4%
IT Infrastructure Monitoring
 

Featured Reviews

Keerthi Kumar Sangaraju - PeerSpot reviewer
Technology Manager at a tech services company with 10,001+ employees
Stable, easy to set up, flexible, and has multiple functionalities, but needs to define priority levels for each incident
What's lacking in Loom Systems is the level of priority for each incident. For example, after implementation and there was a huge impact on the client, and the client comes back to you and says that there's an incident, that there needs to be an immediate resolution for it, you'll see severity one, severity two, etc., in Loom Systems, rather than priority levels. It would be better if the incidents can be defined as low priority, medium priority, or high priority.
Dhananjay Dileep - PeerSpot reviewer
Senior Software Engineer at a consultancy with 10,001+ employees
Unified monitoring has improved end-to-end visibility and reduced detection time across apps
When we have too many detectors in place for one particular app, such as when I have created 50+ detectors through my account, the entire page becomes a bit loaded when creating the 51st detector, feeling heavy and taking time to load. Additionally, it throws random errors; for example, when we try to save one detector, it might throw some random error which is not even related, with something else being wrong, not that particular error, but the underlying root cause might be different. Sometimes the error is just "some problem occurred," and we are not able to point out what the real cause is. This mainly happens when we have too many detectors or too many alerts in place rather than a standard number. One more thing is in the alert rules; if we have a main general alert, and instead of creating a new detector, we are adding a new rule under one detector, when the number of rules also increases, such as when we have 10 or 15 rules under one generic detector, that again creates the same kind of problem, taking some time to save that particular newly added rule, and it might not save at times, just keeps on spinning. Those are the two drawbacks which I spotted recently; other than that, everything looks perfect.

Quotes from Members

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

Pros

"The RFS portion of the solution is the product's most valuable feature."
"What I like best about Loom Systems is that you can use it for infrastructure monitoring. I also like that it's a flexible solution."
"The solution is absolutely scalable. If an organization needs to expand it out they definitely can."
"You can develop your own apps within Loom, and they can be configured very simply."
"The product's deployment phase is good and very easy because it is done with OpenTelemetry for most of the parts."
"It's a very easy-to-use solution."
"Splunk Observability Cloud has helped improve my operational performance; previously, we used Elastic for similar purposes, and this has allowed us much more visibility into what we're working on with usable dashboards and metrics, which has been awesome."
"Splunk's GUI and dashboard capacity are the most valuable features of Splunk Infrastructure Monitoring."
"The ability to create custom dashboards is one of the best features and that's typically why most people deploy Splunk. Users can create dashboards for just about anything."
"I have definitely seen a return on investment with Splunk Observability Cloud, particularly through how fast it has grown and how comfortable other teams are in relying on its outputs for monitoring and observability."
"The most valuable thing that we have seen within our group is the ability to ingest all this raw data and have it organized in a certain way so that different groups can get effective alerting from this massive amount of raw data that is out there."
"The most valuable feature in this solution is the log searching."
 

Cons

"What's lacking in Loom Systems is the level of priority for each incident. For example, after implementation and there was a huge impact on the client, and the client comes back to you and says that there's an incident, that there needs to be an immediate resolution for it, you'll see severity one, severity two, etc., in Loom Systems, rather than priority levels. It would be better if the incidents can be defined as low priority, medium priority, or high priority."
"The discovery and mapping still takes a lot of human intervention, it's quite resource heavy,"
"The reporting is a bit weak. They should work to improve this aspect of the product."
"The change management within the solution needs to be improved. There needs to be more process automation."
"The product collects a lot of data but it does not assure that it collects all of it."
"There are always areas for potential improvement to enhance its functionality and user experience."
"Splunk Observability Cloud could be improved with better integration with AppDynamics, as we know that's coming, however, it is an issue we've had between the OpenTelemetry and the AppDynamics collector."
"The only strain point we've encountered with Splunk Observability Cloud is that the search times can be lengthy for some things. We have a large environment, so that's expected."
"The solution's stability is an area that has room for improvement. It needs to provide constant stability to its users."
"The end-to-end visibility is lacking because Splunk cannot directly monitor network devices."
"The UI of Splunk Observability Cloud is one of the major issues; it's old and has been there for more than 10 years, acquired by other applications from other companies. It's time to reinvent how the UI is going to work with the AI modules and integrations, making it softer and cleaner."
"Splunk APM's performance could be improved - at the moment, it's very slow and takes forever to give me what I want."
 

Pricing and Cost Advice

Information not available
"The solution's pricing is costly."
"I am not in that circle, but we are currently licensing based on our queries. That is working out for us. Previously, it was by volume of data, and now, we can store as much data as we want."
"Splunk Infrastructure Monitoring is an expensive solution."
"Splunk APM is expensive."
"Splunk has been fairly expensive, but it has been predictable."
"Licensing cost is the biggest argument I get from those divesting from Splunk. There are those within our organization who say we are going to go to other tools since Splunk is too expensive."
"It is expensive."
"Splunk Observability Cloud is expensive."
report
Use our free recommendation engine to learn which IT Infrastructure Monitoring solutions are best for your needs.
881,114 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
No data available
Financial Services Firm
13%
Computer Software Company
10%
Manufacturing Company
10%
Retailer
8%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
No data available
By reviewers
Company SizeCount
Small Business20
Midsize Enterprise10
Large Enterprise47
 

Questions from the Community

Ask a question
Earn 20 points
What do you like most about SignalFx?
The most valuable feature is dashboard creation.
What needs improvement with SignalFx?
Regarding dashboard customization, while Splunk has many dashboard building options, customers sometimes need to create specific dashboards, particularly for applicative metrics such as Java and pr...
What is your primary use case for SignalFx?
The solution involves observability in general, such as Application Performance Monitoring, and generally addresses digital applications, web applications, sites, and mobile applications. I worked ...
 

Also Known As

No data available
Splunk Infrastructure Monitoring, Splunk Real User Monitoring (RUM), Splunk Synthetic Monitoring
 

Overview

 

Sample Customers

Citrix, Amdocs, Sysaid, Hexaware, Effibar, Revtrak, Taptica
Sunrun, Yelp, Onshape, Tapjoy, Symphony Commerce, Chairish, Clever, Grovo, Bazaar Voice, Zenefits, Avalara
Find out what your peers are saying about Loom Systems vs. Splunk Observability Cloud and other solutions. Updated: January 2026.
881,114 professionals have used our research since 2012.