ManageEngine OpManager vs Pico Corvil Analytics comparison

"The integration with the firewall monitoring, the security monitoring, is great."

"Some of the useful features are NetFlow and analytics."

"The alerting feature has improved our organization. We can create multiple alerts and refine them to how we need to use them."

"We don't have to keep an eye on it; it has a good automation option, which keeps us informed. It gives very less false positives. Overall, a really great product."

"The solution offers very good integration capabilities."

"Desktop central products feature dashboards that are neat and offer comprehensive information."

"The traffic monitoring and the traffic analysis are great."

"We have found the solution to be stable."

"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."

"The analytics features of Corvil are really good... As long as you know what the field is in the message, you can build your metrics based on that field... It means you can do the analytics that you actually care for. You can customize it..."

"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."

"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."

"We can use CLI with the UI for configuring the new monitoring system, which is good."

"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."

"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..."

"I would like to see more enhancements made to the product."

"The only problem with it is that the setup isn't very intuitive. I know that they just upgraded the product to make it a little bit easier to use, but compared to some of the other platforms, it is not easy to configure it, set it up, and get it running. However, once you have set it up and got it running, it runs great."

"It is sometimes difficult to manage the user interface. It can get very complicated."

"We encounter challenges in monitoring cloud services. I would also appreciate it if there was someone available to walk you through the documentation."

"The solution's reports need to include the number of applications consumed."

"The pricing of the solution is high. They should work to adjust the pricing model to see if they can help reduce costs."

"For the implementation part, I am facing issues when configuring the business view. When I create the business view, I experience problems with the port interface."

"What I'd like ManageEngine OpManager to improve on is artificial intelligence. In particular, the machine learning feature should be integrated with the sensor flow. Doing this will give leverage, especially when you look at other products such as the Cisco DNA Center. When a switch goes down, I should be able to build on the correlation of other physical devices it's connected to so that I can integrate that with my CA CMDB. The ManageEngine OpManager team needs to draw a long-term roadmap where that feature becomes an integral part of the solution because right now, machine learning in ManageEngine OpManager is a long process. The solution doesn't have MLS search and I want to see ML being developed and applied for CA CMDB to greatly reduce the burden of tying everything. For example, if I have a data center switch that goes down now, I should know what server it's connected to, and when that switch goes down at twenty-four ports, I would get twenty-four alerts for different devices plugged in. I should be able to make a correlation that the major problem lies in the switch and not with the twenty-four elements connected to that switch. That is where machine learning should come into play and the ManageEngine OpManager AI should indicate "This is where the root of your problem is." It could be difficult, but this is a feature that should be improved or added to the solution."

"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."

"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."

"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."

"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."

"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."

"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."

"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."

"Alerting isn't great... you can only put in one email address in. And that's for all kinds of alerting on the box."

"The price for ManageEngine OpManager is average."

"I rate the tool's pricing an eight out of ten."

"The solution's pricing is very low compared to other products."

"Pricing for ManageEngine OpManager depends on the number of nodes you onboard and whatever pricing is reflected on the ManageEngine portal which offers discounts from ten percent to fifteen percent. It purely depends on the sales volume and the negotiation. In my organization, there are about one thousand two hundred nodes which cost around $29,000 per year. There's no additional support fee or maintenance fee from ManageEngine OpManager. Pricing for the solution is highly competitive and I would rate it five out of five. ManageEngine OpManager is one of the most competitive options out there."

"We had perpetual licenses. The cost was around 36,000 for OPManager, and then you'd have the yearly maintenance fee of 2,000 or 3,000."

"The tool's licensing costs are yearly."

"The solution is highly affordable"

"As far as cost, it was around six hundred thousand rands ($40,500) for the year, for the renewals. That's the total cost for a four thousand node system including support and maintenance."

"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."

"It is pricey versus its competitors."

"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."

"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."