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
77
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

reviewer2045373 - PeerSpot reviewer
SENIOR CLOUD SUPPORT ENGINEER at a financial services firm with 10,001+ employees
The flexible dashboard sets it apart from competing tools, but it's costly and lacks scalability
Geneos provides near-real-time data if the underlying infrastructure is sufficient. The time to get a response depends on the kind of alert you set. All monitoring tools have multiple alert methods. You can receive an alert within the tool where it flags the issue on the dashboards. You get real-time alerts in Geneos. You can also receive alerts via email. That is quick unless your email system has some delay latency. Geneos sends alerts within 20 to 30 seconds. It will throw the alert to your inbox and 13 chatbots. You can configure Geneos with chatbots also in real-time. The primary benefit to our company is the dashboard. We have a management dashboard that highlights business-critical alerts to management. We have a high-level dashboard for management and a technical dashboard for L2 and L3 engineers. The help desk and other L1 departments have their own dashboard. The dashboard has improved our business significantly because it provides visibility into the entire operation from one screen. It offers a traffic-light mechanism. When there is an issue in North America or South America, Geneos immediately alerts you and the management that there is something we need to look into. Geneos can predict and resolve problems through automation. Geneos will automatically restore the service several times when a service goes down based on our configuration. It prevents a couple of outages each month where the services do not come back online following a server restart.
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

"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"
"ITRS uses SNMP to communicate with our devices as well as SNMP net probes installed on our servers."
"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."
"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 great advantage of this tool is real-time monitoring."
"The solution's log monitoring and alerting mechanisms are very user-friendly and easy to plug and play."
"I always appreciate Geneos's stability and ease of use."
"The NetProbe carries over 100 samplers which are capable of monitoring hardware, OS, and the application layer."
"Great monitoring of network devices."
"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."
"I find the monitoring console very helpful. With one click, I can see how we are performing, and at the same time, I can see what data is flowing."
"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 tool is efficient in collecting, monitoring and evaluating logs."
"Splunk Infrastructure Monitoring reduces our mean time to resolve. We are more proactive than reactive."
"Dashboards help the application support teams to have a quick look at how their systems are running. It helps other teams as well."
"The most valuable feature is the ability to customize dashboards based on my queries or any other customization I may need."
 

Cons

"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."
"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."
"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."
"There is one drawback to using lightweight data collection: we lack the feature of observability based on time series, such as historical model data. This makes it difficult to view data in ITRS. ITRS needs to improve this feature."
"The dashboard feature is full of bugs. Grouping items results in a distorted dashboard."
"Currently, it is difficult to monitor secure websites using SSL or with SSO enabled."
"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."
"​It needs to be easier to configure, especially with the JMX plugins.​"
"The user interface of Splunk Observability Cloud needs a lot of work."
"The solution's stability is an area that has room for improvement. It needs to provide constant stability to its users."
"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."
"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."
"The RUM part of Splunk Observability Cloud can be improved significantly."
"The dashboards are used mainly to visualize information about the infrastructure, but it isn't easy to construct or use the dashboards. While we tried to resolve the issue by calling support, it would be easier if they had an AI co-pilot to identify the problem and help you solve it."
"The feedback is that Splunk Observability Cloud is forcing me to modify my logs that I am ingesting in Splunk Observability Cloud in a specific format."
"Particularly what we're having is disconnection from the cloud console, where we will be working in it and receive a message saying that we've been disconnected and have to wait for it to come up."
 

Pricing and Cost Advice

"Pricing and licensing is based on the requirements."
"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."
"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 seems reasonable. We're happy enough with it."
"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."
"You will get the best price if you get a single global deal."
"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."
"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."
"This is an expensive solution."
"Splunk APM is expensive."
"It is expensive."
"The product is a bit expensive considering the competition but the company may negotiate the price."
"The pricing is reasonable."
"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."
"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."
report
Use our free recommendation engine to learn which Application Performance Monitoring (APM) and Observability solutions are best for your needs.
881,360 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 Enterprise49
 

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,360 professionals have used our research since 2012.