Need advice about which tool to choose?Ask the StackShare community!
Sensu vs Zabbix: What are the differences?
Sensu vs Zabbix
Sensu and Zabbix are both popular monitoring tools used in IT infrastructure. While they share the common goal of monitoring and gathering data from systems, there are key differences that set them apart. Here are the 6 key differences between Sensu and Zabbix:
Scalability: Sensu is designed to be highly scalable and is well-suited for large-scale and complex environments. It uses a distributed architecture that allows for easy scaling and handling of a high volume of checks. On the other hand, Zabbix is also scalable but is better suited for medium-sized environments due to its centralized architecture.
Flexibility: Sensu provides greater flexibility in terms of customizing and extending its functionality through plugins and custom handlers. It allows users to write checks in different programming languages, making it more adaptable to various use cases. Zabbix, on the other hand, is more rigid in terms of customization options and primarily relies on built-in monitoring templates.
Ease of Use: Zabbix offers a user-friendly web interface, making it easy to navigate and set up monitoring quickly. It provides a wide range of predefined templates, graphs, and dashboards that simplify monitoring configuration. Sensu, on the other hand, has a steeper learning curve and requires more expertise to set up and configure. It provides less out-of-the-box functionality and requires more manual configuration.
Versatility: Sensu is known for its versatility and can monitor a wide range of systems, including cloud-based infrastructures, containers, and microservices. It can integrate with various technologies and tools to gather data from different sources. Zabbix, while capable of monitoring various systems, is more focused on traditional infrastructure and may require additional configurations for newer technologies.
Alerting: Sensu excels in its flexible and robust alerting capabilities. It provides fine-grained control over alert routing and allows integration with popular notification systems like PagerDuty, Slack, and OpsGenie. Zabbix also offers alerting features but may not be as flexible or have the same level of integration options as Sensu.
Maintenance and Support: Sensu is an open-source tool with a strong and active community that provides continuous support and regular updates. It also has a commercial offering that provides additional enterprise-level support. Zabbix, on the other hand, is primarily supported by its vendor, Zabbix SIA, with both community and enterprise editions available.
In summary, Sensu offers scalability, flexibility, and versatility, making it suitable for large and complex environments that require extensive customization and integration capabilities. Zabbix, on the other hand, provides ease of use, strong alerting features, and good support, making it a solid choice for medium-sized environments with more traditional infrastructure. Choose Sensu for advanced customization and complex environments, while Zabbix provides simplicity and solid functionality for more standard use cases.
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 Sensu
- Support for almost anything13
- Easy setup11
- Message routing9
- Devs can code their own checks7
- Ease of use5
- Price4
- Nagios plugin compatibility3
- Easy configuration, scales well and performance is good3
- Written in Go1
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 Sensu
- Plugins1
- Written in Go1
Cons of Zabbix
- The UI is in PHP5
- Puppet module is sluggish2