Zabbix is an open-source network performance monitoring software. It includes prebuilt official and community-developed templates for integrating with networks, applications, and endpoints, and can automate some monitoring processes.
For either DB2 or zLinux, Tivoli is hands-down the best solution. For Oracle and other operating systems, there are more advanced solutions available. Some of these features are considered "game-changing" by our Sys Admins. Of the three solutions I've dealt with, Tivoli ranks right in the middle with cost, features, and complexity. A nice solution (and the best for the options I listed above), but not cutting-edge.
Zabbix is very well suited for infrastructure monitoring i.e. the underlying host servers, basically, compute nodes. However, it has limited FM & PM capabilities for the workloads, i.e., the virtual machines (VMs). Zabbix has an easy-to-use GUI which can be explored easily & provides good filtering of the data.
Collecting hardware data - CPU, Memory, Network, and Disk Metrics are collected and reported on.
Flexible design - It is very easy to build out even very large environments via the templating system. You can also start where you are - network monitoring, server monitoring, etc. and then build it out from there as time and resources permit.
Provides a "plugin architecture" (via XML templates) to allow end users to extend it to monitor all kinds of equipment, software, or other metrics that are not already added into the software already.
Very complete documentation. Almost every aspect of Zabbix has been documented and reported on.
Cost - Zabbix is FOSS software and always free. Support is reasonably priced and readily available.
Tivoli is not manageable from the GUI console and I believe it needs a dedicated resource to manage the software.
Tivoli (TSM) configuration is complex, granular, and scalable with customizable configuration features, but it requires a good administrator that has a strong knowledge of the product.
It needs additional agents or plugins for administration; for example, I have to use an MMC plug-in on the servers.
In a busy Zabbix environment, it can easily overwhelm the underlying database. Plan on having SSDs and a significant server infrastructure to keep up with more than a hundred hosts.
Building out Zabbix metrics that suit your environment can be very time consuming. When choosing a monitoring platform like Zabbix, expect a steep learning curve and to invest significant resources to make the tool valuable.
This is less important than it has been in the past, but current versions of Zabbix still do not handle IPMI checks of hardware very well. We needed to write our own wrapper for IPMI checks rather than using the built in IPMI poller.
It is free. It didn't cost anything to implement (other than my time and the cost incurred for it) and it is filling a badly needed gap in our IT infrastructure. Support is available if we have issues and can be done annually or paid for on a per incident basis as needed. Expansion, updates, and all other future lifecycle activities are likewise free of cost, so as long as someone is able to implement/maintain the software (and the OSS project is maintained) then I imagine the company will never leave it.
The setup is the most time-consuming portion of using zabbix. It takes a lot of effort to shape it into a usable format and even then it can get very messy. It's not exactly intuitive and as mentioned the UI seems a bit antiquated. If I was to roll out a monitoring solution from scratch, I'd probably look for alternatives which are easier to use and maintain.
We are a mainly Windows environment, so it would be useful if we could have used Active Directory to deploy agents. As of version 4.2, Zabbix has announced a new agent MSI file to allow exactly that. Unfortunately, we didn't have that option. Also, for Linux and MAC deployments, there is no simple way to deploy that. Using remote scripts you may be able to create something, but most places will opt for either SNMP (agentless) or manual installation of agents to add to Zabbix. A way of deploying agents via discovery would go a long way to helping in the adoption of the tool.
Tivoli sits right in the middle of these two products, all things considered. Each has its own strengths (Cohesity has bells and whistles, CommVault works well with Microsoft). Tivoli is a nice blend and rock-solid once implemented.
We're using the Solarwinds suite as our global monitoring standard, but it is very complex and its licensing model makes it difficult to monitor a wide range of technologies. So, we're using Zabbix as a complement on our monitoring process. Zabbix is a way more flexible and has free integrations to a wide range of technologies. It is also more 'user friendly' and easy to manage.
Zabbix simply makes it easier to identify, and subsequently resolve problems quickly
Zabbix gives one web page to look at to see a list of all on-going issue in a single place
Zabbix can automate response to alerts. For example, Zabbix allows you the customization to take a monitored server out of production rotation if it is identified as unhealthy
