Cisco Encrypted Traffic Analytics (ETA) vs. Icinga

Icinga is a world-class monitoring system. It can be used for most general monitoring situations. It is not a silver bullet, however, and there are instances where domain-specific monitoring systems are necessary. However, the output from those monitoring systems can be funneled into Icinga as a central monitoring and alerting system.

Incentivized

• Wealth of community-developed plugins.
• Stable codebase.
• Icinga 2 supports distributed monitoring.
• Very performant, can support tens of thousands of checks per server.

Incentivized

• High learning curve, setting up Icinga from scratch can be a bit of a challenge starting out.
• If the io2db process fails you UI stops updating, which can be very frustrating.
• There is no simple mechanism for adding new hosts and services through the web UI, it's all very config-file based.

Incentivized

Icinga is a solid solution which does everything it promises. It is backwards compatible with most Nagios instances, making the transition very easy. Once you get the hang of installing new plugins and editing configuration files expanding its monitoring capabilities are easy.

Incentivized

Icinga is better than Nagios because of its nicer user interface. New Relic can monitor CPU/memory and disk usage, but it's more of a performance and application troubleshooting tool rather than monitoring

Incentivized

• With one check you know which applications are faulty e.g. after an upgrade. Which is big time saver
• You easily detect outages ion the applications so that your customer ideally does not even realize there was an outage.
• Detect if the environment does deliver the same result as in the same time as before to detect shortages.
• Additional information when debugging. Saved us several hours where we could simply point to a database which was slow.

Incentivized