We performed a comparison between NetBrain and Zabbix based on real PeerSpot user reviews.
Find out in this report how the two Network Troubleshooting solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI."This product has good network monitoring and troubleshooting capabilities."
"NetBrain is a very simple tool."
"Chain management is a good feature. I don't get it on other solutions."
"A reliable, time-saving tool for providing accurate layer 2 and layer 3 network mappings."
"Enables maps to be drawn out."
"They've already added extra features, such as noise-canceling and facial recognition, which is great."
"The product is very stable."
"Setup was straightforward. Initial deployment took two or three months."
"Zabbix has a roadmap and they are continuously and frequently adding new features."
"The flexibility of this solution is amazing."
"Simple network monitoring that is easy to install and manage."
"Zabbix is very easy to implement."
"Zabbix is both stable and scalable."
"The IP interface brief isn't consistent."
"Each device needs to be configured to allow NetBrain to poll for the information it needs, which can be very time-consuming for a large network."
"It would be nice if the setup was a little simpler. Also, if the solution could provide more training materials for new people coming into our company so they can quickly learn how to use the functionalities."
"Support needs to improve for the installed product and some of the reporting could be more flexible to provide more complete cataloging."
"The solution could integrate more automation."
"The performance reporting could be improved."
"Its UI should be improved. They did some improvements in version 5, but it could benefit from some more work. Its integrations should also be improved. They've been active for one year, and they seem to have noticed that. It has new integrations, but it could benefit from more integrations. As far as I know, there is no model to push statistics, metrics, or events towards Zabbix. This type of API isn't yet there, whereas some other tools provide an API for this."
"I would like to see a more flexible mobile client, and better HA out of the box."
"When using this solution in enterprise monitoring, you are able to see that there are some issues with equipment that could be causing a problem. Sometimes you want to make a root command that you do not want to be executed automatically. What we have tried to do is open an SSH session directly from the solution's interface but it is not possible."
"The reporting features need improvement, especially detailed inventory reporting. Since it's freeware, reporting may not be a major focus."
"The documentation could be improved."
"In terms of user-friendliness, large maps could be more interactive. We should be able to click on some areas and move some objects. It would make it simpler to see things while analyzing some dedicated parameters."
"When we have a problem, we have to do a lot of research to solve it."
Earn 20 points
NetBrain is ranked 15th in Network Troubleshooting while Zabbix is ranked 1st in Network Monitoring Software with 101 reviews. NetBrain is rated 7.2, while Zabbix is rated 8.2. The top reviewer of NetBrain writes "Good monitoring and troubleshoot capabilities, improves overall network traffic visibility". On the other hand, the top reviewer of Zabbix writes "Allows any number of customizations but lacks functionality for finding root causes". NetBrain is most compared with Cisco DNA Center, ThousandEyes, Red Hat Ansible Automation Platform, SolarWinds Network Automation Manager and LogicMonitor, whereas Zabbix is most compared with Centreon, Checkmk, Nagios Core, Amazon CloudWatch and SolarWinds NPM. See our NetBrain vs. Zabbix report.
We monitor all Network Troubleshooting 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.
