Need advice about which tool to choose?Ask the StackShare community!
Observium vs Zabbix: What are the differences?
Introduction
Observium and Zabbix are both network monitoring tools that provide valuable insight into the performance and availability of network devices. While they share similar goals, there are key differences that set them apart.
Ease of Use: Observium shines in terms of ease of use, providing a straightforward and user-friendly interface. Its emphasis on simplicity makes it an excellent choice for small to medium-sized networks. On the other hand, Zabbix offers more comprehensive features and customization options, but it requires a steeper learning curve.
Scalability: Zabbix is particularly suitable for large-scale environments due to its ability to monitor thousands of devices simultaneously. It boasts a distributed architecture and supports multiple monitoring agents, making it highly scalable. Observium, while still scalable, might face limitations in handling large networks and may require additional resources.
Alerting and Notification: Zabbix excels in providing advanced alerting and notification features. It supports various alerting methods, including email, SMS, and mobile push notifications. Observium, although it offers basic alerting capabilities, may require third-party integrations or additional configurations for more advanced notifications.
Device Support: Observium focuses primarily on network devices, making it an ideal choice for network administrators. It provides extensive support for network equipment manufacturers, including Cisco, Juniper, and HP. In contrast, Zabbix offers broader support for different types of devices, such as servers, applications, and virtual machines, making it more versatile for monitoring various aspects of an IT infrastructure.
Community and Documentation: Zabbix benefits from a large and active community, contributing to regular updates, numerous integrations, and extensive documentation. This vibrant community ensures quick bug fixes, feature enhancements, and reliable support. Observium, while featuring an active community, may have a slightly smaller user base, resulting in fewer available resources and community-driven plugins.
Pricing and Licensing: Observium provides a free community edition, but its full version requires a commercial license. Zabbix, on the other hand, is fully open-source, allowing users to benefit from all its features without any licensing fees. This difference in licensing models can be a critical factor for organizations with strict budget constraints.
In Summary, Observium and Zabbix differ in terms of ease of use, scalability, alerting and notification capabilities, device support, community and documentation, as well as pricing and licensing models. Choosing between the two depends on the specific needs and requirements of the network monitoring project.
My team is divided on using Centreon or Zabbix for enterprise monitoring and alert automation. Can someone let us know which one is better? There is one more tool called Datadog that we are using for cloud assets. Of course, Datadog presents us with huge bills. So we want to have a comparative study. Suggestions and advice are welcome. Thanks!
I work at Volvo Car Corporation as a consultant Project Manager. We have deployed Zabbix in all of our factories for factory monitoring because after thorough investigation we saw that Zabbix supports the wide variety of Operating Systems, hardware peripherals and devices a Car Manufacturer has.
No other tool had the same amount of support onboard for our production environment and we didn't want to end up using a different tool again for several areas. That is the major strong point about Zabbix and it's free of course. Another strong point is the documentation which is widely available; Zabbix Youtube channel with tutorial video's, Zabbix share which holds free templates, the Zabbix online documentation and the Zabbix forum also helped us out quite a bit. Deployment is quite easy since it uses templates, so almost all configuration can be done on server side.
To conclude, we are really pleased with the tool so far, it helped us detect several causes of issues that were a pain to solve in the past.
Centreon is part of the Nagios ecosystem, meaning there is a huge number of resources you may find around in the community (plugins, skills, addons). Zabbix monitoring paradigms are totally different from Centreon. Centreon plugins have some kind of intelligence when they are launched, where Zabbix monitoring rules are configured centrally with the raw data collected. Testing both will help you understand :) Users used to say Centreon may be faster for setup and deployment. And in the end, both are full of monitoring features. Centreon has out of the box a full catalog of probes from cloud to the edge https://www.centreon.com/en/plugins-pack-list/ As soon as you have defined your monitoring policies and template, you can deploy it fast through command line API or REST API. Centreon plays well in the ITSM, Automation, AIOps spaces with many connectors for Prometheus, ServiceNow, GLPI, Ansible, Chef, Splunk, ... The polling server mode is one of the differentiators with Centreon. You set up remote server(s) and chose btw multiple information-exchange mechanisms. Powerful and resilient for remote, VPN, DMZ, satellite networks. Centreon is a good value for price to do a data collection (availability, performance, fault) on a wide range of technologies (physical, legacy, cloud). There are pro support and enterprise version with dashboards and reporting. IT Central Station gathers many user feedback you can rely on both Centreon & Zabbix https://www.itcentralstation.com/products/centreon-reviews
We highly recommend Zabbix. We have used it to build our own monitoring product (available on cloud -like datadog- or on premise with support) because of its flexibility and extendability. It can be easily integrated with the powerful dashboarding and data aggregation of Grafana, so it is perfect. All configuration is done via web and templates, so it scales well and can be distributed via proxies. I think there also more companies providing consultancy in Zabbix (like ours) than Centreon and community is much wider. Also Zabbix roadmap and focus (compatibility with Elasticsearch, Prometheus, TimescaleDB) is really really good.
Hi Vivek, what's your stack? If huge monitoring bills are your concern and if you’re using a number of JVM languages, or mostly Scala / Akka, and would like “one tool to monitor them all”, Kamon might be the friendliest choice to go for.
Kamon APM’s major benefit is it comes with a built-in dashboard for the most important metrics to monitor, taking the pain of figuring out what to monitor and building your own dashboards for weeks out of the monitoring.
Pros of Observium
- Modern Graphs1
Pros of Zabbix
- Free21
- Alerts9
- Service/node/network discovery5
- Templates5
- Base metrics from the box4
- Multi-dashboards3
- SMS/Email/Messenger alerts3
- Grafana plugin available2
- Supports Graphs ans screens2
- Support proxies (for monitoring remote branches)2
- Perform website checking (response time, loading, ...)1
- API available for creating own apps1
- Templates free available (Zabbix Share)1
- Works with multiple databases1
- Advanced integrations1
- Supports multiple protocols/agents1
- Complete Logs Report1
- Open source1
- Supports large variety of Operating Systems1
- Supports JMX (Java, Tomcat, Jboss, ...)1
Sign up to add or upvote prosMake informed product decisions
Cons of Observium
Cons of Zabbix
- The UI is in PHP5
- Puppet module is sluggish2