We performed a comparison between Spiceworks and Zabbix based on real PeerSpot user reviews.
Find out in this report how the two IT Infrastructure Monitoring solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI."The solution can find all asset details automatically, whether it's a Mac address, computer name, IP address, models, etc. It's very helpful."
"It shows the users that are currently logged in, which is not something that Active Directory by default will ever let you know up front."
"Spiceworks' dashboard allows you to drill down to the notes, where I can take an inventory of the network and see the devices I need to monitor."
"The nice thing about Spiceworks is always it's free. Monitoring of printers for low toner. Finding machines that have low memory or low hard disk space."
"Tickets by e-mail, with actions by hastag."
"The solution is very stable. It's reliable and efficient."
"Spiceworks is generic and free."
"If you're in the market for a low-cost service desk system, Spiceworks is a good software solution to start out with, especially when it comes to startups and those organizations that don't currently have any existing service desk software in place."
"Simple network monitoring that is easy to install and manage."
"It can send messages to our ticketing system."
"The solution allows for good integration with other products."
"In terms of customization and integration, we have more flexibility. We can automate configurations, define deletion rules, and customize based on the needs. The client interface allows for further configuration, making it quite comprehensive."
"The features I found most valuable are the user interface and a wide range of network devices that are easy to configure."
"The most valuable features of Zabbix are flexibility and a single interface for different types of monitoring."
"I'm supervising all the IT departments, and Zabbix seems quite good for them. It provides graphics and information in real time. We get alerts about crashes on the system, enabling us to quickly repair issues. We can easily find devices with problems."
"The integration with third-party tools and the alerts are most valuable."
"Sometimes, it can be difficult to integrate what you need."
"There are a lot of disadvantages to Spiceworks because it's not an agent-based solution."
"The network mapping could be improved. Putting together an actual bonafide network map would be really nice."
"With Spiceworks, like, when I open the websites, I have to Zoom in. I need to zoom in on those websites sometimes because it makes it horrible to use."
"One of the biggest ways in which Spiceworks could improve is by developing better and more automated workflows. For example, in another solution called ServiceDesk by ManageEngine, you can have levels of approval in the event that there is a request for new software, or when someone requests a VPN or WiFi connection. This kind of multi-stage approval feature provided by ServiceDesk does not appear to exist in Spiceworks, and it is one of their main shortcomings for me."
"The SNMP sniffer requires a lot of work to get right."
"They've also tried to integrate it with social logins, like Twitter and LinkedIn, and that type of login authentication has no place in a corporate application."
"Once a device was recognized on the network, Spiceworks never got rid of it even after you took it off the network. You had to go in and manually remove it."
"Look and feel."
"I would like for this solution to be more cloud-friendly."
"Implementing Zabbix is difficult. I've deployed many solutions over the years, and Zabbix is the hardest to implement. You have to do some development to get it to work with IBM, Micro Focus, or HP products."
"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."
"As far as improvements, sometimes I get a bit frustrated when I move from a previous version to a new one because some configuration has changed—I need to investigate the documentation to deal with some configuration. But it doesn't take much time, so it's okay."
"Outside of the normal standard monitoring, I would like to extend patching, importing patching, and supporting patching for Windows Servers."
"The solution needs to add remote features."
"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."
Spiceworks is ranked 32nd in IT Infrastructure Monitoring with 47 reviews while Zabbix is ranked 1st in IT Infrastructure Monitoring with 98 reviews. Spiceworks is rated 7.8, while Zabbix is rated 8.2. The top reviewer of Spiceworks writes "Good low-cost service desk system, but lacks in automation workflows and categorization ". On the other hand, the top reviewer of Zabbix writes "Allows any number of customizations but lacks functionality for finding root causes". Spiceworks is most compared with Lansweeper, ServiceNow, Freshdesk, ManageEngine ServiceDesk Plus and Nagios Core, whereas Zabbix is most compared with Centreon, Checkmk, SolarWinds NPM, Nagios XI and Nagios Core. See our Spiceworks vs. Zabbix report.
See our list of best IT Infrastructure Monitoring vendors.
We monitor all IT Infrastructure Monitoring 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.