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

ITRS Geneos 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

ITRS Geneos
Ranking in Application Performance Monitoring (APM) and Observability
35th
Ranking in Network Monitoring Software
64th
Ranking in IT Infrastructure Monitoring
44th
Average Rating
8.2
Reviews Sentiment
7.1
Number of Reviews
57
Ranking in other categories
No ranking in other categories
Splunk Observability Cloud
Ranking in Application Performance Monitoring (APM) and Observability
7th
Ranking in Network Monitoring Software
7th
Ranking in IT Infrastructure Monitoring
7th
Average Rating
8.2
Reviews Sentiment
6.9
Number of Reviews
78
Ranking in other categories
Cloud Monitoring Software (6th), Container Management (6th), Digital Experience Monitoring (DEM) (2nd)
 

Mindshare comparison

As of February 2026, in the Application Performance Monitoring (APM) and Observability category, the mindshare of ITRS Geneos is 1.0%, down from 1.3% compared to the previous year. The mindshare of Splunk Observability Cloud is 2.3%, up from 1.5% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Application Performance Monitoring (APM) and Observability Market Share Distribution
ProductMarket Share (%)
Splunk Observability Cloud2.3%
ITRS Geneos1.0%
Other96.7%
Application Performance Monitoring (APM) and Observability
 

Featured Reviews

DeepakR - PeerSpot reviewer
Site Reliability Engineer(Observability) at Sapiens
If one server fails, the agent will automatically be reinstalled
ITRS Geneos is a legacy system. It predicts or provides proactive measures once an issue is resolved. It doesn't offer any predictive capabilities or root cause analysis. They throw a lot of data if there's a 90% error. You need to check which process is consuming more CPU and determine the root cause for yourself. You need to troubleshoot it manually. This legacy system could introduce predictive analysis and root cause identification. They are reluctant to switch to newer solutions, which may require writing queries to fetch data. Manually logging into servers, checking CPU usage, identifying processes, and determining root causes is time-consuming. Once the root cause is identified, the issue can be resolved efficiently. The manual troubleshooting process is time-consuming. The content is not openly available in the market. If you search for it somewhere, it is not readily accessible. If you want to try it out, no trial version is available. Therefore, it will be challenging to learn. Loading ITRS is difficult, as you need to purchase it first. Secondly, only a few people are knowledgeable about ITRS in the market, making it challenging to find resources. Thirdly, the documentation must be well-documented, making finding content or training material hard. The UI also needs to be updated, which adds to the difficulty.
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

"I would say that it is an easy-to-use monitoring tool. Amongst the available monitoring tools, it is a really good option."
"One of the most valuable features of ITRS Geneos is the active time feature that helps with the trading applications that I support."
"I always appreciate Geneos's stability and ease of use."
"Ability to monitor logs for potential issues to prevent app outages before problems get a chance to arise. That's invaluable for our teams in a fast-paced trading environment."
"The biggest benefit of Geneos is the fact that we can clearly see, if we have an alert, where that alert has come from. We can see the data around that alert and anything that might be relevant is also shown. We can very easily right-click and see why we've received that alert. That's the best part about it, that you've got all the data there with the alerting."
"This tool allows one to analyse, integrate and customize as per the systems and allows you to set your own rules."
"ITRS uses SNMP to communicate with our devices as well as SNMP net probes installed on our servers."
"It enables us to monitor application processes, to do log-monitoring on a 24/7 basis, to do server-level monitoring - all the hardware parameters - as well as monitor connectivity across applications to the interfaces."
"Splunk Observability Cloud has enhanced our operational performance and our company's resilience, ultimately contributing to improved customer satisfaction."
"What I appreciate most about Splunk Observability Cloud is the correlation feature, specifically the ease of correlating logs and issues to those traces to see where within the path of the business function is failing."
"The data collection from our VMs, containers, databases, and backend components is valuable."
"Splunk Infrastructure Monitoring gives us complete visibility without the need for storage."
"Splunk Real User Monitoring (RUM) has one great advantage in that if they have SAP users, they can monitor their SAP applications."
"The feature of Splunk Observability Cloud that I prefer most is the easy deployment on the cloud."
"Splunk Observability Cloud has helped improve our operational performance and company's resilience, which was their initial offering."
"It is a good tool. It allows you to set alerts for application and infrastructure monitoring, and it allows you to create dashboards."
 

Cons

"One thing that could be improved in terms of rapid scaling would be more ability to clone aspects of an implementation. It seems like there are opportunities in this area, where we have repetitive tasks to do when it comes to implementing things on new servers or on new gateways. It would be great if there was an easy way to clone something that had already been done."
"One area where there is room for improvement is the log file. I would like to be able to do a pre-run on the log files. When you are testing log files for regular expressions, it would be good to be able to do a quick check up front on that side of things before you release that into production."
"I would like ITRS Geneos to develop an app, where instead of going to specific login terminals or logging into laptops or desktops to check alerts, we can have visibility in the app itself."
"I would really like to see something from the Geneos side to set up automated reporting from ITRS. We have to send reporting to management every day. To do that we have to check the dashboard and then we have to report whether everything is fine or not. In the future, I want something, some reporting kind of feature in ITRS, where it can collect all the data and mention what is green, what is amber, what is red in a report."
"Sometimes, if there is a lot of data coming onto the servers, we have observed a little bit of slowness on the gateway servers which are doing the ITRS dashboard monitoring."
"ITRS have started to make some major changes that we haven't taken on board yet, in the creation of dashboards and more visibility of the metrics that we collect. At the moment, that's something that's lacking, but I know they have addressed it. Still, it’s not that easy to create stuff to help with visibility and dashboarding in Geneos."
"t needs to have better middleware integration for things such as application and Microsft SQL servers."
"The ITA, the post-incident analytics, could be improved."
"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."
"It would be useful if they provided some help pages. If you don't know too much about the tool, there should be more documentation readily available. It would be useful if they had a help button embedded in the solution so you could ask questions and get answers."
"The only strain point we've encountered with Splunk Observability Cloud is that the search times can be lengthy for some things."
"The cost needs to be re-examined. It's extremely expensive to run. It's also expensive to expand. That's the number one complaint all of my customers have when it comes to Splunk. It's way too expensive compared to other solutions."
"Primarily, the logs in Splunk APM can be challenging to navigate and comprehend, making it difficult to understand the details within each log. Compared to other tools like LogDNA, which are more intuitive in this aspect, the logs in Splunk APM can require more effort to understand."
"Splunk Observability Cloud could be improved in terms of integrations with more technical add-ons, such as Zoom."
"It would be beneficial to have more enhanced features with capabilities to adapt more integrated applications. Improvements in dashboard configuration, customization, and artificial intelligence functionalities are desired."
"There's no standard use case available where you can see the utilization of the number of use cases I have."
 

Pricing and Cost Advice

"Its price is reasonable. It isn't too expensive, and it isn't too cheap, but it also depends on a company's volume and negotiation."
"You will get the best price if you get a single global deal."
"Pricing is the touchy subject, even here. Upper management always wants us to find a cheaper solution. But we have so much integrated with ITRS... It's expensive, but it does its job very well. And you set it and go."
"The licensing cost may seem expensive upfront. However, the service is outstanding, the tool does things that no other tools can do, and the customizability more than makes up for the cost of licensing."
"ITRS Geneos is not a cheap tool. It's a moderate price for the banking industry. The reason we are not able to add the ITRS monitoring tool for the non-banking industries, and non-finance industries, is that the pricing is too high."
"When I first came in, their pricing was very high. ITRS had a high expectation of what their price should be based on perceived value. I think they have been realizing, more recently, that there are other competitors, so their pricing is a lot better. Licensing for on-premise is okay, however I feel there is quite some work to be done for cloud and containers. We're still working with them to try and work out what that pricing should look like."
"The pricing seems reasonable. We're happy enough with it."
"The organization is not just purchasing a license for the product, but also managing services and professional services from ITRS. Another factor is if the implementation is going to be in production, non-production, or both."
"The product is a bit expensive considering the competition but the company may negotiate the price."
"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."
"Splunk Infrastructure Monitoring is an expensive solution."
"The pricing is based on several factors, including the scale of deployment."
"It is expensive."
"The solution's pricing is costly."
"This is an expensive solution."
"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."
report
Use our free recommendation engine to learn which Application Performance Monitoring (APM) and Observability solutions are best for your needs.
881,565 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
69%
Computer Software Company
5%
Construction Company
3%
Outsourcing Company
2%
Financial Services Firm
13%
Computer Software Company
10%
Manufacturing Company
9%
Retailer
7%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business6
Midsize Enterprise12
Large Enterprise39
By reviewers
Company SizeCount
Small Business20
Midsize Enterprise10
Large Enterprise50
 

Questions from the Community

What is your experience regarding pricing and costs for ITRS Geneos?
The pricing is high. Licensing fees might be around 500$ per server monthly.
What needs improvement with ITRS Geneos?
ITRS Geneos is a legacy system. It predicts or provides proactive measures once an issue is resolved. It doesn't offer any predictive capabilities or root cause analysis. They throw a lot of data i...
What is your primary use case for ITRS Geneos?
ITRS offers multiple products, including upgrades for synthetic monitoring and a SaaS platform. Geneos is used for infrastructure monitoring, covering KPIs such as CPU, memory, processes, network l...
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

Geneos
Splunk Infrastructure Monitoring, Splunk Real User Monitoring (RUM), Splunk Synthetic Monitoring
 

Overview

 

Sample Customers

ITRS Geneos is used by over 170 financial institutions, including JPMorgan, HSBC, RBS, Deutsche Bank and Goldman Sachs. Clients range from investment banks to exchanges and brokers.
Sunrun, Yelp, Onshape, Tapjoy, Symphony Commerce, Chairish, Clever, Grovo, Bazaar Voice, Zenefits, Avalara
Find out what your peers are saying about ITRS Geneos vs. Splunk Observability Cloud and other solutions. Updated: February 2026.
881,565 professionals have used our research since 2012.