Azure Network Watcher vs Fortra's Intermapper comparison

"Azure Network Watcher provides valuable features based on your specific requirements and use cases, helping you monitor network bandwidth, throughput, data flow consumption, and control costs by giving insight into egress and ingress traffic, total input and output operations, bandwidth, and threats through IP identification."

"We use the solution to monitor network services. It helps to capture any network issues."

"The solution is stable."

"The most valuable feature of Azure Network Watcher is the cloud-native application firewall, which is helpful for securing databases."

"This will help the company or the administrator, by helping them see how the traffic moves, to make sure that no entities are having any communication issues or different endpoints with task issues."

"The stability is very good. I rate it a ten out of ten."

"What I like most about Azure Network Watcher is that it's focused more on the architecture. I also like that it has a packet capture feature that tells you how the packet travels and whether it's exiting Azure, etc."

"The most valuable feature of Azure Network Watcher is the cloud-native application firewall. It is helpful for securing databases."

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

"The graphical alerting with the ability to obtain a quick overview of a monitored device is my favorite feature."

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

"The solution has a couple of features which are really interesting; it's not a fancy or expensive solution but we wanted to have a cost effective one and it's doing its job pretty well."

"Put Intermapper in as your base to start from, hands-down."

"Right now, it is really a combination of network topology, network monitoring, and network analyzing, so, in my opinion, it is awesome."

"It's not the most friendly or straightforward to set up. I don't see the value versus the way you have to set it up at first."

"Azure Network Watcher needs to have better documentation and it needs to capture information accurately."

"The solution could improve by limiting the need to clarify the logs. When the clarification is minimized, it is better for everyone involved."

"I still use Wireshark and Azure Network Watcher to get the required data. My team captures the traffic from Azure Network Watcher, downloads it, then imports that traffic into Wireshark to get more details on the number of hits and replies, for example. If you can do that on Azure Network Watcher and have Wireshark built-in, that would make Azure Network Watcher better. If Azure Network Watcher has that functionality where you won't need a third-party tool to get what you need, that would be helpful. I'm also expecting more from Azure Network Watcher. It's more complex than knowing how the IP flows from its source to the destination. The tool also needs more open-source features, such as having some built-in Wireshark that improves monitoring for customers. Sometimes, you encounter a VPN tunnel, network, or routing issue, but finding out more about the blockage is challenging. Is it one hundred percent an Azure issue? Is it a peer issue? You don't get complete information from Azure Network Watcher, so you must use other tools and depend on your strategies to resolve a specific issue. If more features could be added in the next release of Azure Network Watcher, specifically ones you can find on open-source tools, then that would be a plus point for the tool."

"The initial setup and deployment could be improved to be simplified."

"There are some occasional downtimes, but these were based on Azure-specific issues."

"The solution could use some additional components of the network culture, not only VMs. I'd like to see some additional security features because what they currently have concentrates only on the network."

"Azure Network Watcher could improve by having other built-in applications, for example, an application to log activities for inbound and outbound traffic."

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

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

"I'd love to see more of the network management side of it coming back into it."

"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 have seen instances where Intermapper does not seem to recover from network changes."

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

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

"Azure Network Watcher is a little bit expensive."

"The price of the solution is reasonable."

"Price-wise, I have no information on how much Azure Network Watcher costs."

"The pricing is good. It's not too expensive."