We performed a comparison between Azure Network Watcher and Nagios XI 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."
"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 solution is stable."
"We use the solution to monitor network services. It helps to capture any network issues."
"I like the visibility."
"The solution is good for monitoring device behavior."
"The most valuable feature of Azure Network Watcher is the cloud-native application firewall. It is helpful for securing databases."
"The most valuable features I have found are typology, visualization, and capture."
"The most valuable feature of Azure Network Watcher is using the gateways with the connections. The monitoring is useful for the logs and application insights into the data. The traffic filtering issues when it comes to deploying those applications are helpful."
"Nagios XI is stable."
"You want to monitor a specific metric that nobody else has? You can do it even with the most basic of scripting skills, and you can always share it with the vast community of Nagios Exchange."
"I can monitor a software made in-house to software of bigger companies."
"It is an open-source platform with valuable features for performance and stability."
"Nagios XI helped me to draw the network and check for system failures."
"BPI: It allows defining peripherals to map business criticality for efficient monitoring, as required."
"Since this is an open source technology, if we are capable of writing the plugins in any scripting language, this product allows us to monitor anything we want."
"The dashboard allows you to see what's going on in the overall system."
"The Wi-Fi side needs improvement."
"The solution could improve by limiting the need to clarify the logs. When the clarification is minimized, it is better for everyone involved."
"Lacks sufficient security features."
"I would like to see in the future if we can troubleshoot as a firewall because it is equipment as a network player and some diagnostics."
"Azure Network Watcher could improve by having other built-in applications. For example, an application to log activities for in and outbound traffic."
"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 initial learning curve could be improved to be easier."
"Azure is good, however, the Fortinet GUI is more intuitive and I like it more than anything else."
"Azure Network Watcher needs to have better documentation and it needs to capture information accurately."
"I would like to see support for notification via SMS."
"We'd like to see more integration capabilities."
"The reporting part should be made simpler. While we can obtain all the reports we need, we always have to create work-arounds to get them."
"The PNP4Nagios plugin not working easily with XI is an issue for me, because some open source monitoring plugins do not work out of the box. But in the end, you learn to live with it."
"The reporting structure could be more streamlined."
"It is really difficult to integrate Nagios XI with another system to generate logs and alert our management of failures in security infrastructure."
"The product uses the backend as Perl and could be modified to a more lightweight solution like what's being offered by other vendors."
"The scalability of Nagios XI is scalable. However, it is not easy to do."
Azure Network Watcher is ranked 34th in Network Monitoring Software with 9 reviews while Nagios XI is ranked 8th in Network Monitoring Software with 54 reviews. Azure Network Watcher is rated 7.8, while Nagios XI is rated 8.2. The top reviewer of Azure Network Watcher writes "Helpful database security, good support, and beneficial cloud-native application firewall". On the other hand, the top reviewer of Nagios XI writes "Great for monitoring IT services infrastructure with nice tools and helpful notifications". Azure Network Watcher is most compared with Microsoft Network Monitor, Nmap, PRTG Network Monitor, SolarWinds NetFlow Traffic Analyzer and ThousandEyes, whereas Nagios XI is most compared with Zabbix, Nagios Core, PRTG Network Monitor, Icinga and Wireshark. See our Azure Network Watcher vs. Nagios XI 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.
