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

ITRS Geneos vs Pico Corvil Analytics comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Oct 10, 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

ITRS Geneos
Ranking in Network Monitoring Software
64th
Average Rating
8.2
Reviews Sentiment
7.1
Number of Reviews
57
Ranking in other categories
Application Performance Monitoring (APM) and Observability (34th), IT Infrastructure Monitoring (45th)
Pico Corvil Analytics
Ranking in Network Monitoring Software
71st
Average Rating
9.0
Reviews Sentiment
7.1
Number of Reviews
9
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of March 2026, in the Network Monitoring Software category, the mindshare of ITRS Geneos is 0.6%, down from 0.6% compared to the previous year. The mindshare of Pico Corvil Analytics is 0.5%, up from 0.5% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Network Monitoring Software Mindshare Distribution
ProductMindshare (%)
ITRS Geneos0.6%
Pico Corvil Analytics0.5%
Other98.9%
Network Monitoring Software
 

Featured Reviews

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.
Ted Hruzd - PeerSpot reviewer
Founder at AI Fit LLC
Helpful support agents, beneficial issue detection, and high availability
The creation of charts and real-time windows was somewhat cumbersome. The vendor's website had an application called App Agent that required improvement. This API was designed to track message rates between microservers ingested into a microservice memory map. It allowed users to monitor the number of transactions that occurred at specific points within the application, and it was quite impressive. However, it had some limitations, and it mainly served as a tool for basic tracking. The protocols it employed could reveal the type of server-to-server communication and the specific order types, but it was not able to provide a more in-depth analysis of the application. The vendor has the potential to integrate application metrics more extensively into their product suite. The product suite could benefit from more out-of-the-box predictive analytics capabilities, such as projecting market or symbol movements. However, it is unclear whether the vendor currently provides this functionality. Users may need to adjust their software to perform such analysis independently.

Quotes from Members

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

Pros

"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."
"It's also easy to implement. The implementation of Geneos is very easy and interesting. It's not complicated. It's very quick to implement. The installation is very easy. There are many topics about ITRS Geneos that explain more about the features of the function of Geneos."
"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."
"Real-time log monitoring with desktop alerts is valuable as it tells us immediately when there is an issue."
"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 NetProbe carries over 100 samplers which are capable of monitoring hardware, OS, and the application layer."
"I would say that it is an easy-to-use monitoring tool. Amongst the available monitoring tools, it is a really good option."
"Tons of default modules which are available out of the box"
"It allows us to trace the flow. The logic is built sufficiently for us to be able to break down clients' orders, underlying child orders, and execution. Thus, it's a good way for us to trace client flow through a myriad of different internal systems."
"The performance metrics are pretty good. We've got everything from the network layer to the actual application layer. We can see what's going on with things like sending time and batching."
"Time-series graphs are very good for performance analysis. We can do comparisons... We can say this is the latency in the last 24 hours, and this was the same 24-hour period a week ago and overlay the two time-series graphs on top of each other, so we can see the difference. That's a really powerful tool for us."
"It has all the decoders so it's capturing every network packet and it's decoding in real-time and it's giving us latency information in real-time... It's the real-time decoding and getting the latency information statistics that we find the most useful."
"We're able to quickly drill down and find answers to events that are happening in real-time, using Corvil's analytics tools. That's the feature which is most in the spotlight..."
"As part of my role in monitoring multiple client connections, I would use Pico Corvil Analytics to set up alerts for performance issues, such as TCP resends and dropped packets. These alerts would trigger when the volume was low and performance was poor, allowing me to work with our trading partners to find a resolution. I would present them with the statistics I had and together, we would identify the source of the issue. This collaboration resulted in the client often reconfiguring their systems. For example, we may find that a network connection needed to be made. Overall, this proactive approach helped to maintain strong connections with our clients and minimize disruptions to trading revenue."
"We use the data to analyze how much time we spend within the applications. Then, based on that, we are doing multiple analyses and types of investigations to work on reducing the amount of time spent on the latency, which helps our applications."
"We like the dashboards because they essentially organize all the sessions into one viewpoint."
 

Cons

"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."
"At the moment Geneos is excellent and handling real time monitoring, however not great at doing historical reporting."
"Data visualization – real time and historical – is a weakness."
"They have the Webslinger solution where you can see when something is alerting. It's a little bit cumbersome."
"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."
"​It needs to be easier to configure, especially with the JMX plugins.​"
"ITRS Geneos is not on the cloud at a time when everyone is moving to the cloud."
"t needs to have better middleware integration for things such as application and Microsft SQL servers."
"It's quite difficult to see, sometimes, how hard your Corvil is working. When we had a very busy feed that chucked out a lot of data it wasn't working very well on Corvil. We had to raise a case for it. It turned out to be that, in fact, we were overloading Corvil."
"Alerting isn't great... you can only put in one email address in. And that's for all kinds of alerting on the box."
"In terms of performance analysis, if you really want to dig down into the minutiae and get statistics on the important things... that would be the only piece lacking because, in our environment, we have thousands and thousands of symbols. With the architecture that Corvil is built on, it's cumbersome."
"There is definitely room for improvement in the reporting. We've tried to use the reporting in Corvil but, to me, it feels like a bolt-on, like not a lot of thought has gone into it. The whole interface where you build reports and schedule them is very clunky."
"I have seen errors where the CNE and the CMC haven't synced because of something missing in the CMC, which was there in the CNE. We would get some type of error, but it doesn't actually say what exactly was missing in the CNE."
"While the product is scalable, it's not easy to scale. It needs investment hardware and network bandwidth consideration. It's not something you can just do overnight."
"The creation of charts and real-time windows was somewhat cumbersome. The vendor's website had an application called App Agent that required improvement. This API was designed to track message rates between microservers ingested into a microservice memory map. It allowed users to monitor the number of transactions that occurred at specific points within the application, and it was quite impressive. However, it had some limitations, and it mainly served as a tool for basic tracking. The protocols it employed could reveal the type of server-to-server communication and the specific order types, but it was not able to provide a more in-depth analysis of the application. The vendor has the potential to integrate application metrics more extensively into their product suite."
"For FIX protocol, maybe we could have built-in configurations for signatures and decoders. Also, for certain protocols, which are newer, we would like to just add the signatures within the decoders itself."
 

Pricing and Cost Advice

"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."
"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."
"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 seems reasonable. We're happy enough with it."
"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."
"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."
"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."
"Given our spend and the amount of service we have in it, the pricing is quite reasonable."
"As I am working more with Corvil, it looks like it is improving diagnostic times."
"Corvil has reduced the time it takes us to isolate root causes."
"Pico Corvil Analytics is expensive. There are several competitors in the market. Selling this solution to a trading firm might be challenging as there are several other solutions available that can perform basic similar operations, such as using Wireshark and Python scripts to obtain the required values. However, that does not nearly approach the comprehensive end-2-end automated depth of metrics and their correlations that Pico Corvil Analytics provides."
"We bought a box from Corvil and it was $200,000 for one big CNE. Then there are obviously the recurring maintenance fees. The licensing is perpetual but the maintenance fees are not."
"It is pricey versus its competitors."
"I like the way they've decoupled the hardware now... Everything's based on the licensing side now. The way they do the packs is fair. It's very flexible in that we're not charged per decoder, we're charged for a certain pack. Whether we use one decoder or 20 decoders, as long as they're in the same pack, there's no extra charge. Expensive but fair is how I'd summarize it."
"The pricing is very expensive. Corvil could work on the pricing."
report
Use our free recommendation engine to learn which Network Monitoring Software solutions are best for your needs.
883,760 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
69%
Computer Software Company
6%
Construction Company
3%
Outsourcing Company
2%
Financial Services Firm
42%
Computer Software Company
10%
Non Profit
5%
Comms Service Provider
5%
 

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 Business2
Midsize Enterprise1
Large Enterprise6
 

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...
Ask a question
Earn 20 points
 

Also Known As

Geneos
Corvil
 

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.
NASDAQ, Commerzbank, Pico Quantitative Trading, CME Group, Interactive Data, Tokyo Stock Exchange Inc.
Find out what your peers are saying about ITRS Geneos vs. Pico Corvil Analytics and other solutions. Updated: March 2026.
883,760 professionals have used our research since 2012.