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 (35th), IT Infrastructure Monitoring (44th)
Pico Corvil Analytics
Ranking in Network Monitoring Software
70th
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 February 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.6%, up from 0.5% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Network Monitoring Software Market Share Distribution
ProductMarket Share (%)
ITRS Geneos0.6%
Pico Corvil Analytics0.6%
Other98.8%
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

"Custom script toolkits"
"ITRS can define rules to alert when certain parameters that you monitor breach a threshold. Rules can be configured to fire recovery actions automatically to clear the alert"
"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 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."
"The built-in plug-ins allow administrators to easily configure monitoring components for market data systems such as Thomson Reuters Enterprise Platform and SRLabs Wombat (formerly NYSE)."
"The solution's log monitoring and alerting mechanisms are very user-friendly and easy to plug and play."
"This solution has helped provide relief to existing Level 2 teams, allowing them to focus efforts on in-depth problem analysis."
"The great advantage of this tool is real-time monitoring."
"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 can use CLI with the UI for configuring the new monitoring system, which is good."
"What is most valuable is the ability to troubleshoot when a client complains of spikes in latencies. It gives us the ability to go granular, all the way down to looking at the network packets and analyze them."
"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'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..."
"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 like the dashboards because they essentially organize all the sessions into one viewpoint."
 

Cons

"They have the Webslinger solution where you can see when something is alerting. It's a little bit cumbersome."
"I would like ITRS Geneos to develop an app, where instead of going to specific login terminals or logging into laptops or desktops to check alerts, we can have visibility in the app itself."
"​It needs to be easier to configure, especially with the JMX plugins.​"
"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."
"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."
"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."
"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."
"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."
"Alerting isn't great... you can only put in one email address in. And that's for all kinds of alerting on the box."
"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."
"The analytics feature is very nice, but it's mostly software. We are hoping that it could be embedded in ASICs, so it could be faster."
"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."
"Overall, the Corvil device needs a little bit of training for people to handle it. If that could be reduced and made more user-friendly, more intuitive, it would be better."
"Before I got the Corvil training... one thing that was not very efficient was that every time you had to create a new stream or a new session from within Corvil... you had to tell it what protocol the message is going to come through and how to correlate messages, etc... After I went for the training, they had already added these nice features in the 9.4 version where it could do auto-discovery... Based on the traffic that it has already seen, it could create sessions on the fly."
"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."
"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."
 

Pricing and Cost Advice

"You will get the best price if you get a single global deal."
"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."
"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."
"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 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."
"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."
"Given our spend and the amount of service we have in it, the pricing is quite reasonable."
"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 is very expensive. Corvil could work on the pricing."
"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."
"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."
"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."
"Corvil has reduced the time it takes us to isolate root causes."
"As I am working more with Corvil, it looks like it is improving diagnostic times."
"It is pricey versus its competitors."
report
Use our free recommendation engine to learn which Network Monitoring Software solutions are best for your needs.
881,665 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
69%
Computer Software Company
5%
Construction Company
3%
Outsourcing Company
2%
Financial Services Firm
44%
Computer Software Company
10%
Non Profit
6%
Manufacturing Company
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: February 2026.
881,665 professionals have used our research since 2012.