ManageEngine NetFlow Analyzer vs Plixer Scrutinizer comparison

"I give this solution a rating of 10 out of 10 and absolutely recommend it based on our experience."

"ManageEngine NetFlow Analyzer has detection capabilities for flow, event, and service flow."

"It helps us determine what is going on with our Internet and who is hogging it all up. If we get a real high throughput or a throughput that's going over and getting dropped fairly quickly, we can tell who (or what device) is consuming that traffic."

"It's agnostic as far as what your network gear is. As long as it supports an sFlow, JFlow, NetFlow, some kind of flow monitoring, Plixer will support it very well."

"The reporting and generating troubleshooting reports would be the best feature; our host-to-host conversation reporting."

"We didn't experience any bugs."

"The most valuable features of Plixer Scrutinizer are its ease of use, accessibility, and UI."

"Plixer Scrutinizer is an affordable product. Plixer Scrutinizer is a tool that allows for customization, especially in scenarios where customers need new product features."

"There are other tools out there that will do what Scrutinizer does. But what I have found with Scrutinizer is that it does it very quickly. I've taken 25 million individual data fragments from the different sensors, and it has graphed that and mapped it and presented a picture within 30 seconds. It has a very efficient database algorithm that I am really impressed with."

"The most valuable features of the solution are the ability to track what a device is doing and to go back historically. It is also able to go down to, and identify, very low levels of traffic."

"In ManageEngine NetFlow Analyzer, we have to set custom thresholds to get alerted if there is a problem in network connectivity. It would be helpful if we could automate the tool such that we don't have to set thresholds manually, and the tool automatically alerts us when it detects issues."

"Data retention needs improvement. Data retention is a thing where we are looking for a better way to collect flow data for a longer time to do forensic research on security incidents. By default, data retention is quite low. We need detailed data in safe storage for a longer time, e.g., for a couple of months. An improvement would be a way to export data into a secure long-term storage."

"From what I understand it is that the solution is not very scalable in a high volume traffic environment with a large number of flows."

"Knowing that they're coming out with a new user interface, that is an area where there is room for improvement. There are so many variables. They should limit the variables in the user interface and create some classes, like "simple," "novice," and "expert" to narrow down the variables within it."

"We couldn't get it set up properly."

"Though Plixer Scrutinizer has network detection and response, it's an area that needs just a little more rounding out. Another room for improvement in the solution is its lack of SaaS offering which some customers were looking for. My company deals in small to medium businesses, mid-market, and some customers wanted the SaaS feature which Plixer Scrutinizer doesn't offer. What I'd like to see in the next release of the solution is for it to have a SaaS offering because my company also deals with educational spaces and smaller businesses that just don't have the staff that can implement this. If there's either a managed service or SaaS-based offering to just make it a little easier for those types of customers, it would be a great addition to Plixer Scrutinizer."

"It would be useful if there was a way to back up the configuration information. E.g., if you wanted to deploy a new instance or disaster recovery, you could quite easily deploy and restore the config, as opposed to having to restore all the NetFlow data. If there was just a button that said "backup config information", that would be good."

"I wish the reporting side was easier to work with, but it does a decent job. I also wish the reporting side was a little more intuitive or they offered more reporting examples."

"In Plixer Scrutinizer, scalability is an area with minor concerns where improvements are required."

"Our entire solution, amortized over five years, is in the vicinity of $40,000 to $50,000 a year."

"There is a recurring maintenance fee after the initial purchase or if we want the license upgrade."

"Currently, the license for Plixer Scrutinizer is subscription-based and at a yearly fee. The price would depend on the amount of traffic you pull in. For example, there are several blocks from a 10K flow, a 40K flow, and a 100K flow, and based on the number of devices that you receive the flows from, that's the license, and it is not a per-interface pricing model, so that is a very strong, very competitive pricing feature of Plixer Scrutinizer. Licensing for the product is also not based on the number of storage, compared to some competing products that are priced based on the amount of storage you need, particularly based on the retention and the amount of data. Plixer Scrutinizer licensing is based on the device, and it's more in the direction of $10,000 because, with just $1,000, you don't have anything."

"There are no extra costs. It's about $8,000 a year. The bang for the buck (cost) is definitely a plus."

"Compared to some of the other tools we have, it's incredibly reasonably priced."

"We recently bought a license upgrade, so we will integrate more exporters. We upgraded from a 25 exporter license to a 50 exporter license. Therefore, there will be more flows, and this will be an extension. I don't know when we will purchase a faster server, because the server that we have is quite new."

"We have increased the license over time. We have added more licenses as the network has grown."

"The licensing cost for Plixer Scrutinizer is in the middle. It's not the cheapest, but it's not the most expensive. Its licensing model is based on how many exporters, how many devices export information to the system. Plixer Scrutinizer has different modules you could add such as the security module which would cost extra."