Icinga Reviews and Ratings

Use Cases and Deployment Scope

Icinga is used to monitor our internal systems and applications, so that we are detectings outages before the user does. It is also used to monitor out applications, which are in use on customer site.

Likelihood to Recommend

Is is well suited for monitoring of applications and systems both internal and external. Due to the ease to add your own plugins you can monitor your applications as granular as you like.

If you want an easy to use monitoring suite and don't want to spend much time configuring it, PRTG would be a better solution. But if you want to configure many granular details I think Icinga is a good solution.

Use Cases and Deployment Scope

Icinga is used by the hosting and support teams. To give us a dashboard for any current incidents but also to show warnings for us to react before it can become a bigger problem. We also make use of services such as certificate monitoring

Likelihood to Recommend

When incorporated with other services as part of the monitoring stack Icinga is very helpful. Although on its own you will need to keep the dashboard open to get the alerts making it less helpful. Making use of other services such as opsgenie, elastic search, kibana and graphana to name a few.

Use Cases and Deployment Scope

Icinga is our core monitoring platform for all non-Windows systems. However, our Windows group is actively looking to abandon their current platform and implement it for their systems as well.

Likelihood to Recommend

Icinga or its predecessor Nagios seems to be a tool every SysAdmin has had to work with. It's ruggedly simplistic, and utilitarian, but it works, and it's free. I wouldn't call it perfectly fitted to any one type of system, but it's better suited to more than any other system. It'll just work, and if it doesn't, you can make it work with the same difficulty of the initial setup.

Use Cases and Deployment Scope

Icinga is a world-class monitoring system. I've used this product for several companies, monitoring everything from typical server response to verification that specific daemons are up and running. The client/server nature of Icinga allows for monitoring of nearly anything you can write a script for. Installing the client on a server, you can monitor local CPU, memory, processes, etc. without the need for SNMP. Communication between client and server is TLS encrypted, adding security where typically there is none. We have used Icinga across the entire enterprise to monitor network and system devices.

Likelihood to Recommend

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.

Use Cases and Deployment Scope

Icinga was in place when I started, it continues to be used for a legacy environment. It monitors the status and availability of servers and services, previously for the entire production and quality assurance environments and now just for a legacy mail processing system. We chose to move away from Icinga about a year ago.

Likelihood to Recommend

If you're running bare-metal in a datacenter and your hosts are fairly static, it's probably okay to use something like Icinga to monitor your systems. In general, I would not recommend using any monitoring software based on Nagios (Icinga is a fork of Nagios) due to the outdated concepts inherent in those systems. There are a number of good SaaS monitoring solutions which are superior and several open source projects which implement an automation-centric approach to monitoring.

Use Cases and Deployment Scope

Like Nagios, we used Icinga as a network monitoring solution. It provided us with insights as to when a device was not functioning properly or failed completely. It was implemented throughout the entire organization, monitoring all our most critical assets.

Likelihood to Recommend

Anywhere you have critical assets to be monitored Icinga is a good option. In order to make the most use of it, it has to have someone dedicated to supporting it as there are no built-in "auto-discover" new hosts options.

Use Cases and Deployment Scope

Icinga is one of our internal monitoring user interfaces. It's the front end to nagios basically. We incorporate it with our Pager-Duty service and will receive pages if critical services go down. Our technical operations team is the primary department that uses Icinga, however more and more of the engineering and development teams are getting logins as they will be given more responsibility in monitoring their deployed services.

Likelihood to Recommend

Icinga is a good tool for monitoring all aspects of your infrastructure. Because Nagios/Icinga are very customizable, you can monitor anything. I wouldn't use this tool for time series data or trending. There aren't graphs or at least we haven't used the graphing features.