Plixer Scrutinizer Reviews

In terms of additional features I'd like to see in the next release of Plixer Scrutinizer, I can't think of any because you can do some integration with other monitoring tools that are not strong in NetFlow or don't have NetFlow at all. There are also some integration possibilities in the product, plus there are alerts, too. Plixer Scrutinizer is a pretty complete product. There was a price lift because previously the product was privately owned, and now there is some external capital in the organization, so pricing could be lower, though, for Plixer Scrutinizer, there is almost no competition at this price point.

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.

I would recommend having more data points. Plixer Scrutinizer cannot handle high traffic volumes. This is NetFlow Analyzer, and the number of data points, or the massive volume of information is stored. There are numerous processes running inside a router. As a result, a massive amount of data is being logged in this Plixer Scrutinizer. It is my understanding that when the flows are too high, the solution cannot handle them, and it is not simply a matter of scaling it up. For example, on ACI, you can define Cisco ACI core switches, and it is found that on Plixer Scrutinizer they are unable to handle the traffic volume. When I'm talking about a core switch or another switch that has a large amount of traffic flowing through it, the solution is also incapable of handling it. In terms of data aggregation and storage, while I was not managing it, one of the feedbacks, specifically to this solution. I can't comment further on the technical side of things, but from a user standpoint, the team was only keeping the real-time log for one day. Then, for three days, it switches to five-minute aggregation. It switches to one-hour aggregation for one week. For one month, it will be aggregated on a daily basis, to save space. It aggregates the data points and removes the individual real-time data points before reducing the data points to conserve storage. I would suggest an improvement in data storage, or how the data is archived and sold so that enterprises have more room to keep data for a longer period of time with less aggregation. It will be kept for real-time value for a month, rather than just one day.