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

InfluxDB 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

InfluxDB
Ranking in Network Monitoring Software
52nd
Average Rating
8.2
Reviews Sentiment
6.5
Number of Reviews
10
Ranking in other categories
Non-Relational Databases (3rd), Open Source Databases (12th), IT Infrastructure Monitoring (45th), NoSQL Databases (5th)
Pico Corvil Analytics
Ranking in Network Monitoring Software
73rd
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 May 2025, in the Network Monitoring Software category, the mindshare of InfluxDB is 0.3%, up from 0.3% compared to the previous year. The mindshare of Pico Corvil Analytics is 0.5%, up from 0.3% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Network Monitoring Software
 

Featured Reviews

PedroCampos - PeerSpot reviewer
A powerful, lightweight time series database with a simple query language and easy setup
Influx has TICK Stack, which contains multiple services and multiple products that work together. InfluxDB is just a time series database, and it works really well. I haven't yet had the time to look into the new stack based on Influx 2.0, but currently, as a time series database, InfluxDB is working the way it is supposed to work. 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 would also like to have high availability features, such as replication, active-active, etc. If they can put an extra plugin or service on top of it, it would be something interesting. I am not sure if they have high availability to make it data center-aware for clustering. For example, I am not sure whether you can have it at different locations with big clusters that are location-aware. Even in their documentation or presentation, they talk too little about high availability and extended clusters with different locations. They might already have it in the newer versions. We have Influx 1.8 in our production in the stage and internal workloads environments. The other products in their ecosystem, such as Chronograf, can be improved. Chronograf is a dashboarding or visualization layer product, and that, for sure, can be improved.
Ted Hruzd - PeerSpot reviewer
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

"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."
"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 solution is very powerful."
"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 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."
"The most valuable feature of the solution is we can use InfluxDB to integrate with and plug into any other tools."
"With the Corvil Stored Data Analyzer module, we can use it for test data or a set of production data to set up the configuration for latency setup, so we can use the fields to correlate messages."
"We can use CLI with the UI for configuring the new monitoring system, which is good."
"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."
"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."
"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."
"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."
"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."
 

Cons

"The error logging capability can be improved because the logs are not very informative."
"One area for improvement is the querying language. InfluxDB deprecated FluxQL, which was intuitive since developers are already familiar with standard querying."
"The solution doesn't have much of a user interface."
"The solution's UI can be more user-friendly."
"I've tried both on-premises and cloud-based deployments, and each has its limitations."
"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."
"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."
"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."
"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."
"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."
"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."
"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 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."
"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."
"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."
 

Pricing and Cost Advice

"InfluxDB is open-source, but there are additional costs for scaling."
"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."
"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."
"Corvil has reduced the time it takes us to isolate root causes."
"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."
"The pricing is very expensive. Corvil could work on the pricing."
"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."
"As I am working more with Corvil, it looks like it is improving diagnostic times."
report
Use our free recommendation engine to learn which Network Monitoring Software solutions are best for your needs.
850,834 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
15%
Computer Software Company
13%
Manufacturing Company
9%
Comms Service Provider
7%
Financial Services Firm
56%
Computer Software Company
10%
Manufacturing Company
6%
Educational Organization
4%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
 

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?
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 coll...
What is your primary use case for InfluxDB?
I use the solution to store and manage data from various sensors in a production environment. I have developed a system where data from these sensors is communicated through an OPC UA receiver and ...
Ask a question
Earn 20 points
 

Comparisons

 

Also Known As

No data available
Corvil
 

Overview

 

Sample Customers

ebay, AXA, Mozilla, DiDi, LeTV, Siminars, Cognito, ProcessOut, Recommend, CATS, Smarsh, Row 44, Clustree, Bleemeo
NASDAQ, Commerzbank, Pico Quantitative Trading, CME Group, Interactive Data, Tokyo Stock Exchange Inc.
Find out what your peers are saying about InfluxDB vs. Pico Corvil Analytics and other solutions. Updated: April 2025.
850,834 professionals have used our research since 2012.