Zabbix vs Zenoss Cloud comparison

"The resource usage, CPU utilization, disk usage, network monitoring, network performance, and alerting features are invaluable."

"The most valuable features in Zabbix are those that help us overcome bottlenecks in CPU usage, as well as reduce memory delay. I know that we have only reached the tip of the iceberg of what Zabbix's features can do for us, and we have not used all of them yet."

"Dashboard and the customization of the items and triggers are the most valuable features."

"It not only provides the preconfigured item monitoring feature, but it is also easy to configure custom items."

"Zabbix has a roadmap and they are continuously and frequently adding new features."

"The most valuable features are the monitoring and the ease with which we can set it up at customer sites with our custom Zabbix proxy and tools."

"Zabbix is fully scalable, with no limitations in that regard."

"It meets my organizational needs. It's pretty easy to use."

"The custom built integration is one of the most valuable features because you can see all the especially critical items."

"It's easy to use."

"They have also accommodated many state-of-the-art technologies like Docker and ZooKeeper."

"Its Docker Container concept is mind blowing. It is the first monitoring tool which comes with Docker features."

"What I like most about Zenoss Service Dynamics is that it monitors the devices and gives close to real-time alerts. For example, in case the device is not available, Zenoss Service Dynamics generates an alert so my team can resolve the issue."

"The most valuable feature is the flexible discovery mechanism."

"The product offers good documentation that helps with initial training."

"An area for improvement would be the ease of doing aggregation from the value or different devices."

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

"The reports are not great and should be improved."

"Zabbix isn't a great tool for cloud-specific monitoring - its connection to public clouds needs to be improved. Other areas for improvement would be the lack of dashboards and integrations."

"The reporting is lacking because this is an open-source tool, and nowadays, management's expectation is that the reports should be of high quality and every information should be presented in a concise manner."

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

"In the next release, I'm hoping for features targeted towards larger users with more customizable options. Despite this, I think pre-canned reports that can be used straight out of the box would be beneficial rather than having to configure each report individually. Additionally, a deeper dive into software configurations on the machines would be useful, although I understand there may be challenges in implementing this due to scripting requirements. More documentation would also be appreciated."

"If Zabbix had a better dashboard then it would be nice."

"It would be ideal if the product offered sound alerts."

"The inclusion of a feature to show a graphical view of the network would be a helpful improvement."

"The AI aspect needs to improve."

"Now it is stable, but they should design threshold parameters in percentage instead of raw values."

"As Zenoss Service Dynamics is more for network-centric devices and you want to monitor, for example, a server, its services, IP addresses, and interfaces, if it's a network and you're going to monitor multiple items, you'll be charged multiple times. This is what Zenoss Service Dynamics needs to improve to make sure that customers pay just one fee to monitor the entire server. What I'd like to see in Zenoss Service Dynamics in the future is a public cloud monitoring feature, particularly for the Azure public cloud. Another additional feature I'd like to see in the next release of the solution is integration with the Azure public cloud because I know that there are some services from Azure that Zenoss Service Dynamics is currently unable to monitor."

"There was a problem with Zenoss and storage monitoring."

"There is room for improvement with the administrative part. They introduced Control Center to manage things in Zenoss 5. The services that Zenoss provides remained the same, but the administrative part, since they introduced Docker, etc., has become a little complex"

"Zabbix and Grafana are both open source products, we only needed to go to their website and download the application and we began to use them. The solutions are free."

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

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

"Its licensing is fair. It seems to be much cheaper than others."

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

"It’s free of cost."

"It is open source. If you want to have a subscription or official support, you can pay for it. They have different plans, which are not that expensive. The plans are based on per monitoring server, not per monitored equipment. So, it is not at all expensive, and you can also live without the support if you want a cheaper option."

"The solution is open source so is free."

"There are additional costs you'll have to pay apart from the license fee for Zenoss Service Dynamics. I can't remember exactly how much my company is paying because I don't handle the finance part, but the cost is paid annually. On a scale of one to five, with one being the cheapest and five being the most expensive, I'm rating the solution three out of five."

"It depends on the customer, what he wants."

"The pricing depends on the environment, the number of services, and the size of the data center. It can go from $100,000 to a million dollars."

"It is very cost-effective compared to the tools I worked with in the past. The company is gaining a lot with respect to the cost factor. It provides agentless monitoring and in a very cheap way."