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

"One of the most valuable features of ITRS Geneos is the active time feature that helps with the trading applications that I support."
"The remarkable feature of Geneos is the dashboard. Geneos' flexible dashboard sets it apart from other monitoring tools. Other solutions have limitations in their dashboard design and can't be customized as much. The Geneos dashboard allows unlimited creativity."
"Geneos automatically sends email notifications when any batch job fails, the database is down or the website is down. It is automatically monitoring everything and reduces manual effort."
"One thing we're utilizing in Geneos is the Gateway-SQL. That's really helpful for us. Using Gateway-SQL, we are able to merge two different views into one. Suppose we have to check something in the log and that we have to check something in the database and do a comparison before publishing a result. We can achieve that using Gateway-SQL."
"ITRS can define rules to alert when certain parameters that you monitor breach a threshold. Rules can be configured to fire recovery actions automatically to clear the alert"
"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."
"Tons of default modules which are available out of the box"
"The ability to logically normalize data gathered from multiple types of sources via pre-built plugins is extremely powerful. This functionality, coupled with the ability to import custom data via the Toolkit plugin allows Geneos to be leveraged to monitor every system in the enterprise."
"The solution has significantly helped improve my operational performance and my company's resilience by providing real-time insights."
"The feature of Splunk Observability Cloud that I prefer most is the easy deployment on the cloud."
"Initially, before Splunk, we had a long time to resolve issues; now, with Splunk Observability Cloud, we will be able to solve them quickly and know exactly where the issue is."
"The most valuable features include user time tracking and the ability to analyze application load times."
"Splunk APM provides a holistic view of the application. Unlike other APMs, Splunk's service map is quite effective."
"The most valuable feature is the ability to customize dashboards based on my queries or any other customization I may need."
"The features I appreciate the most about Splunk Observability Cloud are the ServiceNow integration feature, which is very seamless, and that's probably my favorite since ServiceNow is big in the observability industry."
"Splunk Infrastructure Monitoring gives us complete visibility without the need for storage."
 

Cons

"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."
"ITRS Geneos cloud monitoring is very weak and can use improvement."
"t needs to have better middleware integration for things such as application and Microsft SQL servers."
"For the last year or two, I've been asking the vendor about the mobile app. This is something that probably everyone asks when they see the tool and they see how powerful it is. If there is any mobile app for this or if there is any way this tool can be more easily accessible other than having a big client installed, it would be great. I know you can build dashboards, et cetera, but there is no quick and easy way. I should be able to download an app, log in, and see my status. That will put this product above everything else out there. I believe it's on their roadmap."
"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."
"The dashboard feature is full of bugs. Grouping items results in a distorted dashboard."
"At the moment Geneos is excellent and handling real time monitoring, however not great at doing historical reporting."
"The ITA, the post-incident analytics, could be improved."
"We still use Splunk Enterprise licensing. A lot of the newer features go into Splunk Cloud before Enterprise. We're not looking to switch our licensing over, so we're falling behind on the newer features."
"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."
"Once you see the issues related to the scalability part, you need to understand that it is a warning triangle. After seeing the warning triangle, you need to realize that you cannot trust any of the numbers you see in the chart because it is not a complete, full data set."
"Splunk APM's performance could be improved - at the moment, it's very slow and takes forever to give me what I want."
"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."
"The clustering part of indexes can be more refined."
"Splunk Infrastructure Monitoring's data analytics can be improved by including suggestions for various types of continuous monitoring."
"Splunk Observability Cloud could be improved in terms of integrations with more technical add-ons, such as Zoom."
 

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."
"Pricing and licensing is based on the requirements."
"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."
"Based on feedback from colleagues and friends working in the financial sector, Geneos is relatively costly. Many companies have been switching from Geneos to Dynatrace, Sysdig, or other monitoring tools in the past two years because of the price."
"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 market tools are on par with this solution, but if the solution included more features, then it would be well within the range for the cost."
"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."
"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."
"Splunk APM is a very cost-efficient solution."
"Splunk Observability Cloud is expensive."
"Splunk has been fairly expensive, but it has been predictable."
"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."
"The solution's pricing is costly."
"It is expensive."
"I would rate the price of Splunk Infrastructure Monitoring as an eight out of ten, with ten being the most expensive."
"It appears to be expensive compared to competitors."
report
Use our free recommendation engine to learn which Application Performance Monitoring (APM) and Observability solutions are best for your needs.
881,515 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,515 professionals have used our research since 2012.