We performed a comparison between InfluxDB and ITRS Geneos based on real PeerSpot user reviews.
Find out in this report how the two Network Monitoring Software solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI."We can manage the entire system across the network and troubleshoot the pain points."
"The single dashboard is a valuable feature."
"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'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."
"The most valuable features are aggregating the data and integration with Graphana for monitoring."
"The user interface is well-designed and easy to use. It provides a clear overview of the data, making it simple to understand the information at hand."
"The solution is very powerful."
"The most valuable feature of the solution is we can use InfluxDB to integrate with and plug into any other tools."
"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."
"The most valuable features of InfluxDB are the documentation and performance, and the good plugins metrics in the ecosystem."
"The solution's log monitoring and alerting mechanisms are very user-friendly and easy to plug and play."
"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."
"The great advantage of this tool is real-time monitoring."
"Ability to monitor logs for potential issues to prevent app outages before problems get a chance to arise. That's invaluable for our teams in a fast-paced trading environment."
"The remarkable feature of Geneos is the dashboard. Geneos' flexible dashboard sets it apart from other monitoring tools. Other solutions have limitations in their dashboard design and can't be customized as much. The Geneos dashboard allows unlimited creativity."
"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 clean and colorful UI and easy to use options like snooze and active times."
"The solution is used across the entire investment banking division, covering environments such as electronic trading, algo-trading, fixed income, FX, etc. It monitors that environment and enables a bank to significantly reduce down time. Although hard to measure, since implementation, we have probably seen some increased stability because of it and we have definitely seen teams a lot more aware of their environment. Consequently, we can be more proactive in challenging and improving previously undetected weaknesses."
"The technical support needs improvement."
"The Wi-Fi side needs improvement."
"The error logging capability can be improved because the logs are not very informative."
"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've tried both on-premises and cloud-based deployments, and each has its limitations."
"The solution doesn't have much of a user interface."
"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."
"The solution's UI can be more user-friendly."
"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."
"InfluxDB cannot be used for high-cardinality data. It's also difficult and time-consuming to write queries, and there are some issues with bulk API."
"The ITA, the post-incident analytics, could be improved."
"Mobile phone integration is probably not as rich as it could be."
"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."
"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."
"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."
"Data visualization – real time and historical – is a weakness."
"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."
More Juniper Mist Premium Analytics Pricing and Cost Advice →
InfluxDB is ranked 46th in Network Monitoring Software with 8 reviews while ITRS Geneos is ranked 17th in Network Monitoring Software with 57 reviews. InfluxDB is rated 7.6, while ITRS Geneos is rated 8.2. The top reviewer of InfluxDB writes "A powerful, lightweight time series database with a simple query language and easy setup". On the other hand, the top reviewer of ITRS Geneos writes "The flexible dashboard sets it apart from competing tools, but it's costly and lacks scalability". InfluxDB is most compared with MongoDB, Cassandra, Netdata, ScyllaDB and Zabbix, whereas ITRS Geneos is most compared with Dynatrace, AppDynamics, Grafana, Prometheus and Datadog. See our ITRS Geneos vs. InfluxDB report.
See our list of best Network Monitoring Software vendors and best IT Infrastructure Monitoring vendors.
We monitor all Network Monitoring Software reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.