Dell CloudIQ vs Zabbix comparison

"CloudIQ allows us to monitor our servers centrally, and we can receive notifications in case of issues, like a potential hard drive failure."

"I rate CloudIQ a ten out of ten."

"It's convenient because you can access it from a mobile device without needing a laptop."

"The dashboard is clear and user-friendly."

"Some of the most valuable features of CloudIQ include its health status alerts, which allow you to see quickly if there is something that needs immediate attention, preventing the need to check each system individually."

"Fewer vulnerabilities have been observed in the four years we have used the solution."

"CloudIQ allows us to monitor our servers centrally, and we can receive notifications in case of issues, like a potential hard drive failure."

"The dashboard is clear and user-friendly."

"There is less computing power needed for scaling."

"The best thing about Zabbix is the integration and the APIs that are included are very fast"

"The solution allows you to configure and customize how you want to collect information from servers or other systems."

"Zabbix is very easy to implement."

"The template system in Zabbix is very beneficial as it saves time in configuration."

"The solution is stable."

"The solution is open-source, easy to manage, and user-friendly making it easy for anyone to use."

"The most valuable feature is the monitoring of virtual machines."

"PowerScale is the only file system offered and that is limiting."

"In terms of improvement, they should enhance the product range."

"The process of upgrading could be streamlined."

"Getting through support has become a difficult thing. Dell's support has degraded since they took over EMC. It's a bit difficult to use."

"The reporting capabilities of this solution could be improved."

"The main limitation of CloudIQ is that it is intended to be used exclusively with Dell hardware."

"Doesn't do well in terms of integrating with technologies other than Dell."

"There is a need for improvement in predictive maintenance, which I assume is somewhat AI-driven."

"The user interface could be a bit better. They could update it a bit."

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

"The only issue I can note is that it's Linux-based, and Linux documentation is not the best."

"There are some features of Zabbix that are not good for reporting. The DX Spectrum solution has better reporting."

"Even though it’s such a powerful monitoring system, it would be more helpful if it had a flexible UI."

"Zabbix is powerful, but it is difficult to understand initially. There are many things that can be improved, but we might not be using Zabbix to its fullest extent. The software has more features than we need."

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

"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 solution is more expensive than NetApp which offers file systems in various price ranges."

"I believe it is a free product because we don't pay for it."

"I was using the free, Community Edition."

"For pricing, it's free. We don't pay anything for it. They open-source the code, and people pay for support."

"Zabbix is open-source so if one wishes to implement it in-house, they must have qualified professionals to set up and optimize databases, Linux/Unix OS, PHP, Apache, and depending on what is monitored, a full-stack network and systems administrator may be needed."

"There are no licenses."

"The tool's licensing costs are yearly."

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

"There is a license required for this solution and we pay annually for our license."

"We pay the subscription for support by year."