Shinken vs Sysdig: What are the differences?

# Introduction
In this comparison, we will explore the key differences between Shinken and Sysdig.

1. **Architecture**: Shinken is a monitoring framework that is a rewrite of Nagios in Python, providing more scalability, flexibility, and extensibility. On the other hand, Sysdig is primarily focused on container monitoring, utilizing eBPF technology to capture system calls and collect detailed container-level metrics.

2. **Technology Focus**: While Shinken is designed for traditional server and network monitoring, Sysdig specifically targets containerized environments, offering deep visibility into containers, Kubernetes, and cloud-native applications.

3. **Alerting Capabilities**: Shinken offers comprehensive alerting features such as customizable escalation policies, advanced scheduling, and integrated notification mechanisms. In contrast, Sysdig provides alerting based on predefined metrics thresholds, which may be more limited compared to the flexibility of Shinken.

4. **Ease of Deployment**: Shinken requires more manual setup and configuration compared to Sysdig, which offers easier deployment through agents installed on hosts or within containers. Sysdig's agent-based approach simplifies the monitoring setup process, especially in dynamic container environments.

5. **Scalability**: Shinken is known for its horizontal scalability, supporting distributed monitoring setups with multiple pollers and distributed schedulers. Sysdig, on the other hand, excels in monitoring large-scale container orchestration platforms like Kubernetes with efficient resource utilization and minimal performance impact.

6. **Community and Support**: Shinken has an active community and a range of user-contributed plugins and extensions. In contrast, Sysdig provides enterprise-level support and a robust commercial offering for organizations requiring professional assistance and guaranteed service levels.

In Summary, Shinken and Sysdig differ in their architecture, technology focus, alerting capabilities, ease of deployment, scalability, and community support.