Likelihood to Recommend This tool was integrated with Control-M, so whenever we receive any job failure, long-running job, job not started yet, etc, we receive an alert against it. This tool is also integrated with Maximo where we receive the incidents as well for it. Alert's color was as per the criticality of the job and that makes it very easy for an associate to act on it to resolve. We have the SLAs for the jobs as per the urgency of the jobs.
Read full review 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.
Read full review Pros This is one of the best monitoring tools. Very simple to user. Color code makes it very simple as per severity. We receive the heartbeat alert every hour that shows the system is running up and fine. We have black, red, yellow, and orange color alerts that show the critical, urgent, major, and minor incidents. Read full review Wealth of community-developed plugins. Stable codebase. Icinga 2 supports distributed monitoring. Very performant, can support tens of thousands of checks per server. Read full review Cons Sometimes color differences of the incidents as per the criticality . We don't receive the heartbeat alerts sometimes. If the tool is down and we don't receive the alerts on the console we wait for the heartbeat alert and it makes some extra delay in resolving things. Read full review 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. Read full review Likelihood to Renew 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.
Read full review Alternatives Considered This is one of the essential tools for monitoring. This tool was integrated with Maximo and Control-M in my organization. So whenever any job failed in Control-M, we receive an alert against it in the IBM Netcool/OMNIbus. We receive the alerts in different colors as per the criticality. Black for critical ones(Sev1), red for urgent (Sev2), yellow for major(Sev3), and orange for minor(Sev4). So it makes an easy to operate and act on the alerts as per the severity. This tool is very user-friendly and easy to use. No additional training is required for the tool to operate, just a simple KT is enough.
Read full review 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
Read full review Return on Investment Color feature of the alerts as per the criticality is the amazing feature. Heartbeat alert is also an unique feature. No additional training is required to use this tool. just a simple KT is enough. Read full review 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. Read full review ScreenShots