Shinken vs Zabbix

Overview

Zabbix

Stacks684

Followers981

Votes66

GitHub Stars5.3K

Forks1.1K

Shinken

Stacks17

Followers39

Votes0

Shinken vs Zabbix: What are the differences?

Shinken vs Zabbix: Key Differences

Introduction: In the realm of monitoring solutions, Shinken and Zabbix are two popular options. While they serve a similar purpose, there are several key differences that set them apart. This article aims to highlight and compare these differences to help users make an informed decision based on their specific needs.

Architecture: Shinken adopts a modular and distributed architecture that allows it to scale across multiple servers, making it suitable for large-scale environments. On the other hand, Zabbix follows a centralized architecture where all data is collected and processed within a single server, making it more suitable for smaller setups.
Flexibility: Shinken offers more flexibility in terms of configuration and customization. It provides a high degree of extensibility through its modular design and allows users to write monitoring plugins in various programming languages. Zabbix, while still customizable, has a more rigid structure and limited extensibility options compared to Shinken.
Ease of Use: Zabbix is often considered more user-friendly due to its intuitive web interface and simple setup process. It provides a wide range of pre-configured monitoring templates, making it easier for novice users to start monitoring their systems quickly. Shinken, on the other hand, requires more technical expertise and configuration knowledge, which may make it less accessible for beginners.
Community and Support: Zabbix boasts a larger and more active user community, which translates into a wealth of online resources, forums, and plugins readily available for users. It also offers professional technical support options for enterprise users. Shinken, while still having an active community, may not be as extensive or well-established as Zabbix.
Scalability: Shinken's distributed architecture allows it to handle large-scale deployments with ease. It can effectively monitor thousands of hosts and services across multiple servers, making it suitable for enterprise-level environments. Zabbix, while it can still handle a substantial amount of monitoring data, may face performance challenges in highly distributed or globally dispersed environments.
Integration and Compatibility: Zabbix offers native support for a wide range of operating systems, network devices, and databases, making it a versatile choice for heterogeneous environments. Shinken, while it supports many popular systems, may require additional configuration or customization to integrate with certain technologies not directly supported out of the box.

Summary: In summary, Shinken and Zabbix differ in their architecture, flexibility, ease of use, community support, scalability, and integration capabilities. Shinken excels in scalability and flexibility for large-scale environments, while Zabbix stands out in terms of ease of use and community support. The choice between the two ultimately depends on specific requirements and the level of technical expertise available.

Share your Stack

Help developers discover the tools you use. Get visibility for your team's tech choices and contribute to the community's knowledge.

View Docs

CLI (Node.js)

Manual

Advice on Zabbix, Shinken

vivek

Jun 8, 2020

Needs adviceon

Centreon

Zabbix

Datadog

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!

795k views795k

Comments

Detailed Comparison

Zabbix	Shinken
Zabbix is a mature and effortless enterprise-class open source monitoring solution for network monitoring and application monitoring of millions of metrics.	Shinken's main goal is to give users a flexible architecture for their monitoring system that is designed to scale to large environments. Shinken is backwards-compatible with the Nagios configuration standard and plugins. It works on any operating system and architecture that supports Python, which includes Windows, GNU/Linux and FreeBSD.
Smart, Highly Automated Metric Collection; Advanced Problem Detection; Intelligent Alerting and Remediation	Easy to install : install is mainly done with pip but some packages are available (deb / rpm) and we are planning to provide nightly build; Easy for new users : once installed, Shinken provide a simple command line interface to install new module and packs; Easy to migrate from Nagios : we want Nagios configuration and plugins to work in Shinken so that it is a “in place” replacement; Plugins provide great flexibility and are a big legacy codebase to use. It would be a shame not to use all this community work Multi-platform : python is available in a lot of OS. We try to write generic code to keep this possible; Utf8 compliant : python is here to do that. For now Shinken is compatible with 2.6-2.7 version but python 3.X is even more character encoding friendly; Independent from other monitoring solution : our goal is to provide a modular tool that can integrate with others through standard interfaces). Flexibility first; Flexible : in an architecture point view. It is very close to our scalability wish. Cloud computing is make architecture moving a lot, we have to fit to it; Fun to code : python ensure good code readability. Adding code should not be a pain when developing;
Statistics
GitHub Stars 5.3K	GitHub Stars -
GitHub Forks 1.1K	GitHub Forks -
Stacks 684	Stacks 17
Followers 981	Followers 39
Votes 66	Votes 0
Pros & Cons
Pros 21 Free 9 Alerts 5 Service/node/network discovery 5 Templates 4 Base metrics from the box Cons 5 The UI is in PHP 2 Puppet module is sluggish	No community feedback yet
Integrations
Slack Jira PagerDuty Grafana Ansible Skype Chef Bugzilla HipChat ServiceNow.com	Nagios

What are some alternatives to Zabbix, Shinken?

Grafana

Grafana is a general purpose dashboard and graph composer. It's focused on providing rich ways to visualize time series metrics, mainly though graphs but supports other ways to visualize data through a pluggable panel architecture. It currently has rich support for for Graphite, InfluxDB and OpenTSDB. But supports other data sources via plugins.

Kibana

Kibana is an open source (Apache Licensed), browser based analytics and search dashboard for Elasticsearch. Kibana is a snap to setup and start using. Kibana strives to be easy to get started with, while also being flexible and powerful, just like Elasticsearch.

Prometheus

Prometheus is a systems and service monitoring system. It collects metrics from configured targets at given intervals, evaluates rule expressions, displays the results, and can trigger alerts if some condition is observed to be true.

Nagios

Nagios is a host/service/network monitoring program written in C and released under the GNU General Public License.

Netdata

Netdata collects metrics per second & presents them in low-latency dashboards. It's designed to run on all of your physical & virtual servers, cloud deployments, Kubernetes clusters & edge/IoT devices, to monitor systems, containers & apps

Sensu

Sensu is the future-proof solution for multi-cloud monitoring at scale. The Sensu monitoring event pipeline empowers businesses to automate their monitoring workflows and gain deep visibility into their multi-cloud environments.

Graphite

Graphite does two things: 1) Store numeric time-series data and 2) Render graphs of this data on demand

Lumigo

Lumigo is an observability platform built for developers, unifying distributed tracing with payload data, log management, and real-time metrics to help you deeply understand and troubleshoot your systems.

StatsD

It is a network daemon that runs on the Node.js platform and listens for statistics, like counters and timers, sent over UDP or TCP and sends aggregates to one or more pluggable backend services (e.g., Graphite).

Jaeger

Jaeger, a Distributed Tracing System

Related Comparisons

Shinken vs Zabbix: What are the differences?

Shinken vs Zabbix: Key Differences

Architecture: Shinken adopts a modular and distributed architecture that allows it to scale across multiple servers, making it suitable for large-scale environments. On the other hand, Zabbix follows a centralized architecture where all data is collected and processed within a single server, making it more suitable for smaller setups.
Flexibility: Shinken offers more flexibility in terms of configuration and customization. It provides a high degree of extensibility through its modular design and allows users to write monitoring plugins in various programming languages. Zabbix, while still customizable, has a more rigid structure and limited extensibility options compared to Shinken.
Ease of Use: Zabbix is often considered more user-friendly due to its intuitive web interface and simple setup process. It provides a wide range of pre-configured monitoring templates, making it easier for novice users to start monitoring their systems quickly. Shinken, on the other hand, requires more technical expertise and configuration knowledge, which may make it less accessible for beginners.
Community and Support: Zabbix boasts a larger and more active user community, which translates into a wealth of online resources, forums, and plugins readily available for users. It also offers professional technical support options for enterprise users. Shinken, while still having an active community, may not be as extensive or well-established as Zabbix.
Scalability: Shinken's distributed architecture allows it to handle large-scale deployments with ease. It can effectively monitor thousands of hosts and services across multiple servers, making it suitable for enterprise-level environments. Zabbix, while it can still handle a substantial amount of monitoring data, may face performance challenges in highly distributed or globally dispersed environments.
Integration and Compatibility: Zabbix offers native support for a wide range of operating systems, network devices, and databases, making it a versatile choice for heterogeneous environments. Shinken, while it supports many popular systems, may require additional configuration or customization to integrate with certain technologies not directly supported out of the box.

Shinken vs Zabbix

Overview

Shinken vs Zabbix: What are the differences?