Need advice about which tool to choose?Ask the StackShare community!
Kiali vs Zabbix: What are the differences?
### Key Differences between Kiali and Zabbix
Kiali is a service mesh observability and management tool that provides insights into the structure and behavior of microservices in Istio service mesh. It offers real-time monitoring, visibility, and easy-to-understand visualizations of service connections, traffic flow, and performance metrics. On the other hand, Zabbix is an open-source monitoring software that tracks the health and performance of various services, servers, and network devices. It offers a wide range of monitoring capabilities such as centralized monitoring, alerting, data collection, and reporting.
1. **Supported Technologies**: Kiali is specifically designed for Istio service mesh, providing detailed insights and monitoring capabilities for microservices within the Istio environment. In contrast, Zabbix is a more general-purpose monitoring tool that can be used to monitor a wide range of technologies, including servers, virtual machines, network devices, and applications.
2. **Data Visualization**: Kiali offers intuitive and interactive graphical representations of service dependencies, traffic flow, and performance metrics, making it easier for users to understand the communication patterns and workload distribution within their microservices. On the other hand, Zabbix provides customizable dashboards and visualizations for monitoring various metrics but may require additional configuration to achieve similar levels of service visualization as Kiali.
3. **Alerting Capabilities**: Zabbix excels in its alerting capabilities, allowing users to set up complex alert conditions, escalations, and notifications based on specific thresholds or conditions. Kiali, while offering some alerting features, may not be as robust as Zabbix in terms of advanced alerting and notification mechanisms.
4. **Ease of Deployment**: Kiali is typically deployed alongside Istio service mesh and integrates seamlessly with Istio components, making it straightforward to set up and configure for monitoring microservices within the Istio environment. On the other hand, setting up Zabbix may require more configuration and deployment effort, especially when monitoring diverse environments and technologies.
5. **Community Support and Documentation**: Zabbix has been around for longer and has a larger user community, resulting in extensive documentation, plugins, and community-generated content that can aid users in troubleshooting issues and extending the capabilities of the tool. Kiali, being more focused on Istio and microservices, may have a smaller community but offers specialized support for Istio-related monitoring and management tasks.
In Summary, Kiali is specialized for Istio service mesh monitoring with emphasis on microservices visualization, while Zabbix is a versatile monitoring tool with broader technology support, advanced alerting capabilities, and a larger user community for support and documentation.
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 Kiali
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 Kiali
Cons of Zabbix
- The UI is in PHP5
- Puppet module is sluggish2