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
33rd
Ranking in Network Monitoring Software
68th
Ranking in IT Infrastructure Monitoring
45th
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
8th
Ranking in Network Monitoring Software
6th
Ranking in IT Infrastructure Monitoring
7th
Average Rating
8.2
Reviews Sentiment
6.9
Number of Reviews
76
Ranking in other categories
Cloud Monitoring Software (6th), Container Management (6th), Digital Experience Monitoring (DEM) (2nd)
 

Mindshare comparison

As of January 2026, in the Application Performance Monitoring (APM) and Observability category, the mindshare of ITRS Geneos is 1.1%, down from 1.3% compared to the previous year. The mindshare of Splunk Observability Cloud is 2.2%, up from 1.4% 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.2%
ITRS Geneos1.1%
Other96.7%
Application Performance Monitoring (APM) and Observability
 

Featured Reviews

Durai CT - PeerSpot reviewer
Head FM Monitoring at a financial services firm with 10,001+ employees
A stable, scalable, and flexible monitoring tool
Real-time data is one of the unique features that ITRS Geneos offers. For example, if there is an impact on a particular server and a particular application, I want to see what the impact is or what the CPU or hardware usage information is, as well as the service in the same application. I can see the real-time data and the impact by accessing ITRS Geneos and looking at the tree. I don't want a tool that tells me when something is broken. I want the tool to tell me when something is going to break. That is the difference between ITRS Geneos and other tools. I want proactive monitoring, not reactive. I don't need to be notified after the fact that something has broken. If something is broken, I get a notification by email, and some of my customers are going to call me. ITRS Geneos provides proactive monitoring. The great advantage of this tool is real-time monitoring. ITRS Geneos not only alerts us but also gives us a real-time view of the data. This is the tool's first great advantage. It is also lightweight and flexible and can adapt to monitor even low-latency systems, which is the tool's second advantage. Another great feature of this tool is its good presentation layer, which allows us to build custom dashboards to present to business stakeholders. This gives them a high-level status of what is being monitored. If we compare ITRS Geneos to other tools, we will find that each one specializes in a specific area, but the ITRS Geneos tool is more comprehensive. This is its great advantage.
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 uses SNMP to communicate with our devices as well as SNMP net probes installed on our servers."
"I would say that it is an easy-to-use monitoring tool. Amongst the available monitoring tools, it is a really good option."
"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 ability to build integrations to tools that are not monitored out of the box is the most valuable feature."
"This tool allows one to analyse, integrate and customize as per the systems and allows you to set your own rules."
"Tons of default modules which are available out of the box"
"One of the most valuable features is that it can be configured by non-developers. It doesn't require development expertise to configure it."
"The solution's log monitoring and alerting mechanisms are very user-friendly and easy to plug and play."
"Great monitoring of network devices."
"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."
"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."
"I manage six tools, but Splunk Observability Cloud is one of my favorites, and I aspire to build my career specializing in it because it has great features, more attention in the market, and is a relatively new tool with promising growth."
"The solution's service map feature allows us to have a holistic overview and to see quickly where the issues are."
"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."
"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 maintenance of Splunk Observability Cloud is very easy; it's manageable."
 

Cons

"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."
"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."
"We all look at the same things - CPU, disk space, paging stats, service status with RAG status on each. That could be provided straight out, saving significant time."
"A lightweight version which could host more than 100 gateways, as we can see slowness while loading all our gateways."
"ITRS Geneos cloud monitoring is very weak and can use improvement."
"​It needs to be easier to configure, especially with the JMX plugins.​"
"I would also like to see suggested guidelines to accomplish a monitoring task. The issue is that ITRS is so flexible that there is more than one way to complete a task, each with benefits and disadvantages."
"Splunk would be better if some tools were integrated to be able to take action on security or network concerns."
"Splunk isn't an ideal tool for application performance management due to the extensive setup required."
"They can get more integration with a few more products. They can also update some of the dashboards that are in there now."
"The monitoring of workloads when using SignalFx could be improved."
"The initial setup of Splunk Real User Monitoring (RUM) was easy. The solution is deployed on-premises."
"The solution's stability is an area that has room for improvement. It needs to provide constant stability to its users."
"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."
"In future updates, I would like to see more predefined monitoring query solutions, which could be more effective."
 

Pricing and Cost Advice

"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 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."
"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."
"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."
"It is expensive. They have to look at the model around when we move to cloud and how that's going to work. The licensing cost does pay off because of the improvements in support to our business."
"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."
"You will get the best price if you get a single global deal."
"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."
"Splunk offers a 14-day free trial and after that, we have to pay but the cost is reasonable."
"The product is a bit expensive considering the competition but the company may negotiate the price."
"Splunk Infrastructure Monitoring is an expensive solution."
"This is an expensive solution."
"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."
"The solution's pricing is costly."
report
Use our free recommendation engine to learn which Application Performance Monitoring (APM) and Observability solutions are best for your needs.
881,282 professionals have used our research since 2012.
 

Top Industries

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

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: December 2025.
881,282 professionals have used our research since 2012.