Opmantek NMIS vs Zabbix comparison

"The installer itself is basically something that can be used as a no-questions-asked type of installer. I can use it with automation tools like Chef and Puppet. I don't have to answer some random questions. I can worry about all that stuff later on in the configuration."

"It allows for variable polling times of devices on the network. Because it's all in text, in general, that obviously makes it easier from the automation perspective as well, to modify configuration on the fly, using Puppet and those kind of tools."

"In my case, I prefer to only poll interfaces that have descriptions, and the ones that don't have descriptions, I don't really want to know about them. It does allow for all these bits and pieces and adjustments, and fine tuning to get it to a point where it works for my needs."

"The big thing is the event management engine, which is really, really nice to use, and it comes at a reasonable price, unlike some of the competitors like Netcool from IBM. Those kinds of tools are hugely expensive and they come as resource-heavy types of solutions. This obviously doesn't require as much hardware, but it does offer similar benefits where you can manage all the events."

"It does have different modules, so you can extend the solution as you need it, or get as little as you need in the beginning, so you don't have to buy a full set of modules. You just buy what you need and expand later on."

"Our customers also like that they don't have to use multiple modules. Micro Focus and major vendors typically require you to buy several modules and plugins. Our customers do not like that. We offer them a single product for all their monitoring needs."

"The initial setup, while not simple, is easier than other products."

"Setup was straightforward. Initial deployment took two or three months."

"It's a very reliable platform and we've never had any issues regarding the scalability or the stability of Zabbix."

"The solution is stable."

"The product is very stable."

"We use Zabbix to monitor our organization's IT infrastructure and workstations. We don't use Microsoft Intune since it's expensive. The tool's real-time alerting system has proved crucial for us, particularly when a new device joins a network that is not one of our own devices. It notifies us about the presence of this new device, allowing us to investigate further. Additionally, it alerts us about disk usage, memory usage, and the software installed on the machine."

"The most valuable feature is that it provides network segregation for server monitoring."

"These kinds of solutions are more node- or device-based solutions. It would be nice in the future if they could be more data-oriented, so it would be easier for me to pull different stats based on ad-hoc requirements; but in a big, centralized database where I can pull specific things, and mix and match the way I want to."

"Its UI needs to be improved a little bit more so that an end-user is also able to handle it. I can handle it, but others should also be able to handle it in a better way. It becomes complex when we are growing and need to add proxies. We need more scalability features and documentation for different use cases. A lot of articles are available, but they need to be in proper documentation. For example, when you have thousands of servers that have to be monitored in different regions of the world, there should be some kind of documentation to describe how you can create proxies and add them. Sometimes, when you are using the database, it can get overloaded. When the network is growing, the number of transactions becomes very high, and the database gets overloaded. There should be information about how to reduce the load on the MySQL database, which is what Zabbix is using. The market is growing a lot, and it should be enhanced for a lot more things. We are currently bringing enhancements at our end for different use cases. For example, when dockerization is going on, how can we check the logs inside the Dockers. We should also be able to monitor and check the number of logins and add features such as SSO login and two-factor authentication as a protocol. These are the security features and concerns that we have to deal with. Currently, we are developing modules to add features to Zabbix, but they should also work on these features."

"There are not too much documentation or manuals. We found the tutorials very easy to understand but do not go deep enough in the use of Zabbix. We need more manuals, proper use, documentation, etc."

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

"When it comes to troubleshooting or technical support, there is usually some time lag."

"Zabbix is not easy to configure, and upgrading is also an issue."

"The server monitoring could be better."

"The product delivers false positives during reporting because of flapping. Other reasonably priced alternatives may have better performance."

"The APM monitoring has room for improvement, although I hear that the new 5.2 version has some improvements in that area, and I'd like to give that a go. I would like to see a few more templates out there for different styles of monitoring. I use the Grafana interface for reporting. I would also like it to have an out-of-the-box ability to email reports. You can create reports, but to be able to email those reports would be really helpful. I've got users who are not interested in logging in and generating a report. They want it all pre-canned and sent to an email address. It would also be really handy if we could pin certain reports up onto platforms such as Teams or SharePoint. A GUI for the proxy server would be cool to have for debugging purposes and for the support teams to have a look at, but I don't know whether that's really feasible to do. I get enough from the log files themselves."

"It is a true open-source solution, so there are no licensing costs."

"The tool's licensing costs are yearly."

"We pay the subscription for support by year."

"My manager is very happy because it doesn't cost anything."

"It's an open-source solution that can be used free of charge."

"The solution is free. However, many open-sourced tools start out free but eventually start charging."

"It is worth every cent to pay or even study to do your own installation."

"I was using the free, Community Edition."