No more typing reviews! Try our Samantha, our new voice AI agent.

ITRS Geneos vs InfluxDB comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Oct 9, 2024

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

InfluxDB
Ranking in Network Monitoring Software
12th
Ranking in IT Infrastructure Monitoring
16th
Average Rating
8.0
Reviews Sentiment
6.7
Number of Reviews
19
Ranking in other categories
Non-Relational Databases (1st), Open Source Databases (7th), NoSQL Databases (6th)
ITRS Geneos
Ranking in Network Monitoring Software
64th
Ranking in IT Infrastructure Monitoring
45th
Average Rating
8.2
Reviews Sentiment
7.1
Number of Reviews
57
Ranking in other categories
Application Performance Monitoring (APM) and Observability (34th)
 

Mindshare comparison

As of April 2026, in the Network Monitoring Software category, the mindshare of InfluxDB is 0.3%, down from 0.4% compared to the previous year. The mindshare of ITRS Geneos is 0.6%, down from 0.6% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Network Monitoring Software Mindshare Distribution
ProductMindshare (%)
InfluxDB0.3%
ITRS Geneos0.6%
Other99.1%
Network Monitoring Software
 

Featured Reviews

Mugeesh Husain - PeerSpot reviewer
Team Lead, Software at Energybox
Time series data has been managed efficiently for IoT sensors but reporting still needs improvement
How InfluxDB can be improved is relevant since for Energy Box, we face certain issues. We have customers worldwide, including the United States, United Kingdom, and Europe, but when we expanded to China two years ago, they indicated that they do not support the cloud version there. Our application is built on the cloud, which required us to create a separate application for Azure China, which was painful for us. The second issue involves frequent version changes. For example, we started with version one, transitioned to version two, and I heard they are considering InfluxDB version three, reverting to earlier practices. InfluxDB should improve without completely changing its approach. Now we have to redo our work for InfluxDB version three. Regarding needed improvements, the documentation is sufficient, but pricing presents a challenge. InfluxDB has standard pricing, which is acceptable for large companies. However, for startups in our position, they should provide special discounts so everyone can utilize it. The pricing should adapt as companies grow, which is a reasonable expectation.
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.

Quotes from Members

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Pros

"The platform operates very quickly. It is easy to configure, connect, and query and integrates seamlessly with Grafana."
"My advice for others looking into using InfluxDB is to use it the same way I did, because it is really stable, easy and friendly to use, and it is a great product overall."
"InfluxDB's best feature is that it's a cloud offering. Other good features include its time-series DB, fast time-bulk queries, and window operations."
"InfluxDB has played a key role in enhancing system reliability and supporting our goal of delivering a seamless, high-quality product."
"The most valuable features of InfluxDB are the documentation and performance, and the good plugins metrics in the ecosystem."
"The most valuable features are aggregating the data and integration with Graphana for monitoring."
"InfluxDB is a database where you can insert data. However, it would be best if you had different components for alerting, data sending, and visualization. You need to install tools to collect data from servers. It must be installed on Windows or Linux servers. During installation, ensure that the configuration file is correct to prevent issues. Once data is collected, it can be sent to InfluxDB. For visualization, you can use open-source tools like Grafana."
"InfluxDB has positively impacted Energy Box by being the best choice for our needs."
"It's definitely the best solution that I've used, as far as real-time monitoring goes."
"Custom script toolkits"
"The ability to completely tailor and customize what it's monitoring is one of its strongest points. A lot of other monitoring tools are good at certain things, but one of my colleagues described it as the “Swiss Army Knife” of monitoring tools. It can do anything you want."
"It’s very easy to install and setup, offers high scalability, and has a low resource use."
"For getting out in front of a problem before it happens, it's absolutely superb."
"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."
"One of the benefits is to have 24/7 automated monitoring of our most critical services; in general, it has drastically increased the visibility of our estate, definitely improved our response times to issues, and enabled us to proactively detect issues and prevent outages as well."
"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."
 

Cons

"However, I do wish the documentation and community resources around Flux were more extensive and beginner-friendly."
"It is challenging to get long-running backups while running InfluxDB in a Microsoft Azure Kubernetes cluster."
"The interface of InfluxDB is so complex and should be made easier for non-technical people."
"InfluxDB can be improved in several ways. The Flux query language needs to be learned, but if there were something similar to SQL or previous options, it would be much easier for users without imposing a learning curve."
"Sometimes, when we write too much data within a minute, the data count becomes excessive, reaching perhaps 100,000 or 500,000 data points, and InfluxDB gives a timeout exception, which we must handle in our application."
"The solution doesn't have much of a user interface."
"In terms of features that I would like to see or have, in the community version, some features are not available. I would like to have clustering and authentication in the community version."
"I chose an 8 out of 10 because there is room for improvement, such as regarding backups and enhanced security through other types of authentication or encrypted data in TLS."
"ITRS Geneos is not on the cloud at a time when everyone is moving to the cloud."
"At the moment Geneos is excellent and handling real time monitoring, however not great at doing historical reporting."
"I had issues scaling it and ended up having to distribute the load over seven gateways."
"The ITA, the post-incident analytics, could be improved."
"Not a ten because when the Gateway was very overloaded it was very hard to monitor the alerts, especially for the product services."
"Much of the reporting outside of the user interface is very basic and requires much customization to be useful."
"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."
"Much of the reporting outside of the user interface is very basic and requires much customization to be useful."
 

Pricing and Cost Advice

"InfluxDB recently increased its price. It is very expensive now."
"The tool is an open-source product."
"InfluxDB is open-source, but there are additional costs for scaling."
"We are using the open-source version of InfluxDB."
"Given our spend and the amount of service we have in it, the pricing is quite reasonable."
"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."
"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."
"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."
"The pricing seems reasonable. We're happy enough with it."
"You will get the best price if you get a single global deal."
"Pricing and licensing is based on the requirements."
report
Use our free recommendation engine to learn which Network Monitoring Software solutions are best for your needs.
885,444 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
No data available
Financial Services Firm
67%
Computer Software Company
6%
Construction Company
3%
Outsourcing Company
3%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business8
Midsize Enterprise4
Large Enterprise8
By reviewers
Company SizeCount
Small Business6
Midsize Enterprise12
Large Enterprise39
 

Questions from the Community

What do you like most about InfluxDB?
InfluxDB is a database where you can insert data. However, it would be best if you had different components for alerting, data sending, and visualization. You need to install tools to collect data ...
What needs improvement with InfluxDB?
One thing I appreciate about InfluxDB is its balance between performance and ease of use, especially with Flux making complex queries accessible. However, I do wish the documentation and community ...
What is your primary use case for InfluxDB?
My main use case for InfluxDB has been mostly for monitoring and analyzing the time-series data related to system metrics, and also tracking logs and API performance. In my current role, I use it t...
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...
 

Comparisons

 

Also Known As

No data available
Geneos
 

Overview

 

Sample Customers

ebay, AXA, Mozilla, DiDi, LeTV, Siminars, Cognito, ProcessOut, Recommend, CATS, Smarsh, Row 44, Clustree, Bleemeo
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.
Find out what your peers are saying about ITRS Geneos vs. InfluxDB and other solutions. Updated: March 2026.
885,444 professionals have used our research since 2012.