We performed a comparison between Kentik and Plixer Scrutinizer based on real PeerSpot user reviews.
Find out in this report how the two Network Monitoring Software solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI."We can manage the entire system across the network and troubleshoot the pain points."
"The drill-down into detailed views of network activity helps to quickly pinpoint locations and causes. All the information is there."
"The most valuable features have been anything around traffic engineering: being able to determine the source or destination of a surge of traffic, whether it's DDoS-related, or a customer just happened to have a sudden uptick in traffic. Being able to tell where that's coming from or where it's going to enables us to do things based on that."
"I am able to do a lot of work on the visualization end to create different visualizations and different ways to get information out of it."
"It offers a simple yet powerful feature of classifying applications, going beyond basic statistics."
"We're pretty happy with the API functionality. It's web, and it's very simple to set up queries. It has served us well and you don't need to be an expert on the API or the product to set these things up."
"The most valuable feature is being able to pull traffic patterns; to and from destinations. We're able to understand where our traffic is going, our top talkers from an AS set, as well as where our traffic's coming from."
"In terms of the solution’s real-time visibility across our network infrastructure, I have not been able to find any other monitoring or netflow visualization tool that gives me the kind of information I get from Kentik. If I need to take a deep-dive into something that I see, it's really easy for me to do that. Whereas with most other things, I have to use five or six other tools to get that kind of data, with Kentik, I have it all in one place."
"We're also using Kentik to ingest metrics. It's a useful feature, and its response time, whenever we're pulling back the data, is higher than our on-prem solution."
"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."
"As a network engineer, the ability to identify what traffic on the link is consuming all the bandwidth at any given time, and provide immediate feedback to the business, is the most valuable feature."
"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."
"One of the most valuable features of Plixer Scrutinizer is the reporting, particularly how easy it is to drill down into the reports. Another valuable feature of the solution is its overall visibility. It's great. I also liked Plixer Scrutinizer in terms of deployment time and that it's very simple to set up. Once you get the appliance set up and connected, the customer starts to see results immediately, versus other solutions where that could take a while."
"The reporting and generating troubleshooting reports would be the best feature; our host-to-host conversation reporting."
"One feature I found most valuable in Plixer Scrutinizer is the very extensive reporting. Reporting is very flexible, though sometimes you need a little bit of support from Plixer Scrutinizer to create custom-made reporting in a very short time. Reporting is a very strong feature of the product."
"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."
"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."
"The Wi-Fi side needs improvement."
"I would like to see them explore the area of cost analysis."
"There is room for improvement around the usability of the API. It's a hugely complex task to call it and you need a lot of backing to be able to do it. I should say, as someone who's not in networking, maybe it's easier for people who are in networking, but for me that one part is not very user-friendly."
"I believe they're already working on this, but I would love for them to create better integrations from network flow data to application performance — tracing — so that we could overlay that data more readily. With more companies going hybrid, flow logs and flow data, whether it be VPC or on-prem, matched with application performance and trace data, is pretty important."
"I consider the pricing model as an area for improvement."
"I've checked out the V4 version of the interface and it's still a little bit clunky for me to use. I still go back to the old interface. That's definitely one that they still need to work on. It doesn't seem like everything that you get in the V3, the older interface, is there. For instance, I was trying to add a user or do the administrative tasks in V4, and I couldn't figure out where I was supposed to do that."
"They're moving more in a direction where they are saying, "Hey, here's information that you may be interested in or may a need," before the question has to explicitly be asked. Continuing to move in that direction would be a good thing."
"The only downside to Kentik, something that I don't like, is that it's great that it shows you where these anomalies lie, but it's not actionable. Kentik is valuable, don't get me wrong, but if it had an actionable piece to it..."
"We asked for a way, regarding the potential networks that exist, to hook Kentik up with external tools like peering DBs to correlate things together and see what we can do... This is all in the [next] beta now."
"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."
"The visual acuity of how it presents data can sometimes be confusing. It takes a bit for people to spin up how to look at the graphs."
"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."
"They're working on the security areas, so it can provide more insight. What they have is still pretty much IP-concentric. If they were to make it IP and URL, they'd be a little bit ahead on that."
"In Plixer Scrutinizer, scalability is an area with minor concerns where improvements are required."
"There is room for improvement around the data that they have on the website about solutions... they should have more templated solutions on their website. Going out and identifying how to do RTP performance with a Cisco router, or how to do application response times in an Arrista data center deployment was where most of the work was... They should spend some more time documenting solutions and putting together white papers."
"For updating the Scrutinizer platform, when we have the actual data, it never happens in one day. Every time we have the data, we are obliged to install a new server in order to integrate the old data, and every time it has a problem. Most of the time, we were obliged to scrap all the data because we couldn't transfer it to the new server. So, it would be very good if they could improve this part."
"The reporting structure, the front-end GUI, also needs some work. It needs some getting used to. It works fairly well, but it's a technical tool rather than a user tool. You have to understand the structure of the databases before you can really use it."
Kentik is ranked 47th in Network Monitoring Software with 12 reviews while Plixer Scrutinizer is ranked 48th in Network Monitoring Software with 15 reviews. Kentik is rated 9.2, while Plixer Scrutinizer is rated 8.6. The top reviewer of Kentik writes " Flexibility for creating reports and gaining more visibility is a definite strength". On the other hand, the top reviewer of Plixer Scrutinizer writes "Advanced reporting runs analytics on NetFlow and provides signature-based recognition of problems in the network environment". Kentik is most compared with ThousandEyes, Arbor DDoS, SolarWinds NPM, NETSCOUT nGeniusONE and Datadog, whereas Plixer Scrutinizer is most compared with SolarWinds NetFlow Traffic Analyzer, Flowmon , Cisco Secure Network Analytics, ManageEngine NetFlow Analyzer and LiveAction LiveNX. See our Kentik vs. Plixer Scrutinizer report.
See our list of best Network Monitoring Software vendors.
We monitor all Network Monitoring Software reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.
