Try our new research platform with insights from 80,000+ expert users

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
11th
Ranking in IT Infrastructure Monitoring
14th
Average Rating
8.2
Reviews Sentiment
6.5
Number of Reviews
17
Ranking in other categories
Non-Relational Databases (1st), Open Source Databases (7th), NoSQL Databases (4th)
ITRS Geneos
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
Application Performance Monitoring (APM) and Observability (35th)
 

Mindshare comparison

As of February 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 Market Share Distribution
ProductMarket Share (%)
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

"InfluxDB has positively impacted Energy Box by being the best choice for our needs."
"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 works as expected with excellent scalability and stability, which is critical for our application."
"It helps me maintain my solution easily because it is very reliable, so we didn't face any performance issues or crashes regarding our queries; we can get the results very fast."
"While I would rate InfluxDB a ten on a scale of one to ten, users should be thoughtful about matching the engine to their specific needs."
"InfluxDB reduced my time to show data without any interruption, also reducing the number of people needed to manage the project; it is very good to have InfluxDB in my project."
"In our case, it started with a necessity to fill the gap that we had in monitoring. We had very reactive monitoring without trend analysis and without some advanced features. We were able to implement them by using a time series database. We are able to have all the data from applications, logs, and systems, and we can use a simple query language to correlate all the data and make things happen, especially with monitoring. We could more proactively monitor our systems and our players' trends."
"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."
"It's a very powerful application monitoring tool across the industry. Many free, open-source tools are available. There are also paid tools, but ITRS Geneos is a real-time application monitoring tool where the user can monitor, self-configure, and manage alerts through their console."
"Custom script toolkits"
"The great advantage of this tool is real-time monitoring."
"The filtering in the Active Console is exceptional. Depending on the user base, some people don't want to see server-level errors, so we have filters set up in the Managed Entities view, which allow us to filter out things that certain groups don't want to see, while allowing them to see other things. It's a great real-time monitoring solution. And you can draw graphs immediately, right from the Active Console, whether they're current graphs or historical graphs."
"One of the most valuable features of ITRS Geneos is the active time feature that helps with the trading applications that I support."
"One of the most valuable features is that it can be configured by non-developers. It doesn't require development expertise to configure it."
"In my experience, being able to monitor our databases is a valuable feature as we can create our own queries and aren't reliant on the in-built ones."
"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

"InfluxDB is generally stable, but we've encountered issues with the configuration file in our ticket stack. For instance, a mistake in one of the metrics out of a hundred KPIs can disrupt data collection for all KPIs. This happens because the agent stops working if there's an issue with any configuration part. To address this, it is essential to ensure that all configurations are part of the agent's EXE file when provided. This makes it easier to package the agent for server installation and ensures all KPIs are available from the server. Additionally, the agent cannot encrypt and decrypt passwords for authentication, which can be problematic when monitoring URLs or requiring authentication tokens. This requires additional scripting and can prolong service restart times."
"I haven't seen a return on investment; unfortunately, I cannot share relevant metrics such as time saved, fewer employees needed, or money saved."
"One area for improvement is the querying language. InfluxDB deprecated FluxQL, which was intuitive since developers are already familiar with standard querying."
"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."
"However, I cannot ignore the challenges I faced while configuring the database with my message brokers, whether Rabbit or Kafka, because the documentation is not properly provided."
"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."
"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."
"InfluxDB can improve by including new metrics on other technologies. They had some changes recently to pool data from endpoints but the functionality is not good enough in the industry."
"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."
"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."
"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 have started to make some major changes that we haven't taken on board yet, in the creation of dashboards and more visibility of the metrics that we collect. At the moment, that's something that's lacking, but I know they have addressed it. Still, it’s not that easy to create stuff to help with visibility and dashboarding in Geneos."
"Data visualization – real time and historical – is a weakness."
"One thing that could be improved in terms of rapid scaling would be more ability to clone aspects of an implementation. It seems like there are opportunities in this area, where we have repetitive tasks to do when it comes to implementing things on new servers or on new gateways. It would be great if there was an easy way to clone something that had already been done."
"I would like to see ITRS integrate its setup editor with a SVN to check-in setup XML after major changes."
 

Pricing and Cost Advice

"The tool is an open-source product."
"We are using the open-source version of InfluxDB."
"InfluxDB recently increased its price. It is very expensive now."
"InfluxDB is open-source, but there are additional costs for scaling."
"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 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."
"I can say it's not that cheap because the licensing is a little bit costly"
"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 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 pricing seems reasonable. We're happy enough with it."
"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."
report
Use our free recommendation engine to learn which Network Monitoring Software solutions are best for your needs.
881,733 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Manufacturing Company
10%
University
9%
Computer Software Company
9%
Financial Services Firm
9%
Financial Services Firm
69%
Computer Software Company
5%
Construction Company
3%
Outsourcing Company
2%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business6
Midsize Enterprise3
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?
Although I didn't encounter any significant challenges, I think that if there was a NoSQL version of InfluxDB, that would also help because I have used the SQL version. I wish InfluxDB were also av...
What is your primary use case for InfluxDB?
My main use case for InfluxDB involved working on a LEO satellite KPI monitoring application, where I gathered latency, throughput, packet loss, jitter, and various types of network data for severa...
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: February 2026.
881,733 professionals have used our research since 2012.