Fortra's Intermapper vs Plixer Scrutinizer comparison

"The most valuable features are its: log history, real-time monitoring capabilities, accuracy - the number of false positives is very low, and the mapping features."

"What is really cool about HelpSystems InterMapper is that because of its SNMP base, you can integrate all different makes and models on the same map. You, of course, can have more than one map, but you have an option to have visibility into the entire network from one centralized system. You can monitor IPs, routers, radios, DC power plants, and UPS. You can do it all from one network management and monitoring solution. That's what really makes HelpSystems Intermapper great. Another great thing about HelpSystems InterMapper is that you can really bundle different probes under one device. You can have a bundled device. You can monitor the physical status of a host based on the IP availability. You can also monitor services and actually see if anything happens. You can quickly determine whether it is the application layer, host layer, or network layer. HelpSystems Intermapper gives such a unique representation of a network. Ever since we started using HelpSystems InterMapper, we don't have to document everything in a detailed format and store it somewhere. Right now, it is really a combination of network topology, network monitoring, and network analyzing. So, in my opinion, it is awesome. When you have your SNMP topology defined, you don't require a dedicated NMS engineer to manage your system, which is another great thing about HelpSystems InterMapper. I see how our operators get so excited by having the ability to map a device or interface and connect interfaces together. HelpSystems InterMapper is also very operator friendly; not just user friendly, but also operator friendly. This is a unique feature, and it works really great."

"It's all today portal-based which is a good feature for us."

"It's a nice graphical interface, a nice map, that relates Layer 1 to Layer 3, virtually instantly, to the Helpdesk support staff. It provides a default place to get critical information so we can deploy our staff."

"We have had many requests to understand in the network which devices are connected to others. Most people don't have this information or are able to establish a map of data flow everywhere around the network. Scrutinizer can really help with this. We are using it to understand who is talking to what, how, and which protocols can help us to improve security and analyze flow."

"The ability to view the status of the top-10 at a glance is helpful. We immediately know which link is over-utilized or heavily used... and it's all in real-time."

"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 most valuable features of Plixer Scrutinizer are its ease of use, accessibility, and UI."

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

"Visualization of the network traffic is the most valuable feature. It allows you to drill into information quite quickly."

"It shows us the saturation of the network of devices. It gives us a clear view of the flows in the network to understand, for instance, planning upgrades in the network to get an idea of what's going on the network on traffic flows. It gives us insight, for instance, on what's going on on our VPN Client. There are a lot of things where it provides very helpful information. It also gives us our security reports with quite detailed information on what's going on in the network, and whether there are data exfiltrations and so on."

"The solution helps to enrich the data context of our network traffic. It allows me to see what applications are most in use on a slightly historical basis, going back a day or week at tops. It allows me to tune QoS or traffic shaping around what's being used. It saves me from having to unnecessarily upgrade, if I don't need to."

"It's a smaller solution so tools are not as advanced as you would find in a larger solution"

"They can do a better job with SLA reporting. It does some basic reporting, but it really doesn't offer the ability to monitor devices by groups, customers, or carrier to give an overall health performance of specifically-defined environments. That's where HelpSystems Intermapper could have done a better job. I would love to see advanced SLA monitoring and reporting in this solution. They already have a lot of ingredients. They already have SNMP polling. It is really about what people are looking for from SLA monitoring, especially someone who looks at the network topology. You want to see your endpoints. You want to see half of your endpoints by simply analyzing ICMP or SNMP-based availability of your endpoints. Having an ability to define your group and how you bring devices into your group would be a huge benefit."

"I'd love to see more of the network management side of it coming back into it. If we were able to run scripts to bounce ports on switches, that would be great. It's asking a lot, but it's actually very doable because I do it through scripting into other products. If we could incorporate that directly into Intermapper, that would be fantastic."

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

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

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

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

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

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

"The solution creates a visual map of a particular location and how the network flows. You need to spend time to generate all those maps. If they could figure out a way to reduce the time needed to generate the maps, that would be great."

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

"The license is per device. We have 50 devices."

"We pay our one-off cost for the licenses, per device, in blocks of 50. And then we pay an annual maintenance fee of about $15,000 Australian, which is, at this point in time, about $9,000 US, for those 250 devices. The upfront costs for the 250-license use, were about $50,000 Australian, which is about $32,000 US."

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

"We just renewed. The pricing is 5,000 euro per year. This is the final price. All tax (20 percent) is included."

"I rate Plixer Scrutinizer's price a three on a scale of one to ten, where one is low price or affordable, and ten is high price or expensive."

"It's about €10,000 a year for initial license and yearly maintenance costs. In addition, the hardware costs are about €10,000 once every five years."

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