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

"It's also easy to implement. The implementation of Geneos is very easy and interesting. It's not complicated. It's very quick to implement. The installation is very easy. There are many topics about ITRS Geneos that explain more about the features of the function of Geneos."
"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"
"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."
"Custom script toolkits"
"The solution's log monitoring and alerting mechanisms are very user-friendly and easy to plug and play."
"The Netprobe is so lightweight compared to the agents that most monitoring tools use. It's really superior to the competition. The agent that is used by almost every competitive tool takes a lot more system resources. It's slower and it requires a greater effort and more compromises in terms of security to install on the monitored servers. With Geneos, because it lives outside the code, it is far easier and far less taxing on the monitored systems."
"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 flexibility of the product is most valuable. It is highly customizable. If you put your mind to it and think of something you could do, there's a good possibility you can get it integrated within the console, if it's not readily available. The simplicity or ease of customization has been valuable."
"The dashboards are the features of Splunk Observability Cloud that I appreciate the most, providing visual representation of all data and text, which has benefited my organization by speeding up people's jobs and allowing a place to monitor all logs, as there are usually thousands of entries coming in which can become very disorderly."
"The best features in Splunk Observability Cloud are the metrics; I can see any logs or anything related to the server or services we want to monitor, and the metrics are a good function."
"I like the fact that Splunk APM makes it easy to connect to the application database and run queries against the data."
"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."
"The initial setup of Splunk Real User Monitoring (RUM) was easy."
"Splunk has drawn our attention to how the network is running. If there are alarms on things that are not functioning, it gives us early warning on problems that could arise."
"Splunk APM has helped us to standardize logging and monitoring procedures."
"Splunk Observability Cloud has enhanced our operational performance and our company's resilience, ultimately contributing to improved customer satisfaction."
 

Cons

"They have the Webslinger solution where you can see when something is alerting. It's a little bit cumbersome."
"For the solution to stay relevant in the cloud-based monitoring environment Geneos needs more plug-ins with more features. Instead of offering clients workarounds, the solution should have a cloud-based out-of-the-box version."
"ITRS Geneos is not on the cloud at a time when everyone is moving to the cloud."
"Their cloud monitoring solution needs to be improved. I have already given them the feedback that it's not capable of meeting the latest technology needs."
"There is a part of the rules for monitoring alerts. I want to understand more about how to choose the samples and the requirements for the rules. That is the part that I want to understand better and get better training for."
"t needs to have better middleware integration for things such as application and Microsft SQL servers."
"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."
"The deployment method for upgrading is a bit tricky. It takes a little bit of manual effort. If that could be a bit more automated, it would help us a lot."
"In Splunk Observability Cloud, I notice room for improvement in synthetic monitoring. It does not provide output based on server names."
"The RUM part of Splunk Observability Cloud can be improved significantly."
"Splunk APM should include a better correlation between resources and infrastructure monitoring."
"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."
"There is room for improvement in customer support due to delays and standard feedback responses."
"Splunk Observability Cloud could be improved in terms of integrations with more technical add-ons, such as Zoom."
"A wide variety of logging makes log onboarding difficult."
"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

"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 and licensing is based on the requirements."
"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 pricing is fairly market-related. They have been very lenient because we have been working with them for so long. An example is that we're currently migrating some of our services to AWS, and they've given us a grace period for some of the things to help with the migration and not to grow additional costs while we are migrating, but it's still on par with the market."
"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."
"Given our spend and the amount of service we have in it, the pricing is quite reasonable."
"The product is priced quite high. There are pricing options for customers based on the size of the environment and plug-ins used by the monitoring system."
"The pricing seems reasonable. We're happy enough with it."
"This is an expensive solution."
"The pricing is based on several factors, including the scale of deployment."
"Splunk's infrastructure monitoring costs can be high because our billing is based on data volume measured in terabytes, rather than the number of devices being monitored."
"The pricing is reasonable."
"The solution's pricing is costly."
"Splunk APM is a very cost-efficient solution."
"It appears to be expensive compared to competitors."
"Splunk has been fairly expensive, but it has been predictable."
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.