Icinga Review

Nice GUI, and the Self-healing event handler automatically restarts system when it is down

What is our primary use case?

Icinga was created as a fork of the Nagios monitoring system. They are similar in graphics and other features, but most who have used Nagios have changed over to Icinga.

It was deployed using our enterprise application to monitor different services.

What is most valuable?

The most valuable feature is one that not many are even aware of. Icinga has an event handler. This solution has a self-healing handler where if the service is down, it is automatically restarted. Not all monitoring solutions offer this feature.

The handler was deployed to take action after the monitoring station has received a critical alarm or a warning alarm. You can configure the handler to take action after the critical alarm without human interaction.

Also, we have used the integration between Icinga and terraform. When Terraform starts using a new VM it communicates to the APIs with Icinga, then puts the machine at the Icinga portal.

The GUI is very good; it is open-source and it's easy to implement.

The NRPE interactions are fine, and the Graphite is good, but there is another source called Grafan and it is better.

What needs improvement?

Development is needed between APIs, Icinga, and the Enterprise. 

One of the areas that are frustrating is remote monitoring for more than one machine. If I have two machines, an X and a Y, and I would like monitors from machine Y, I would have to log into Machine Y and run a separate service. Icinga does not provide this service. It is implemented manually, not automated.

Icinga uses the latest plugins, it does not have its own plugins.

That database monitoring also requires a plugin that is offered with Nagios plugins. The Nagios plugins only monitor the past checks from the database. I would be happy to see more plugin features added.

Also, with the CSV importing, you can import the monitors to our CSV files, unfortunately, this feature did not work for me, it needs to be improved. 

More market awareness of the event handler is needed.

In the next release, I would like to see more plugins, that is number one, more records, and a better dashboard. If they could implement or automate a new dashboard using some colours it would make it easier to navigate through. Icinga dashboard is comparable with other solutions on the market in regards to the dashboard, they are all the same. The users who are monitoring only use the dashboard before they know the features, they don't have the experience.

We can write scripts using Tomcat and Java to make it as a plugin and run it, but it would be better to have more plugins available. The more plugins, the better.

The API between admin and everything for continuous integrations and continuous delivery needs to be improved.

I would like to see some log monitors in the next release. Nagios had some plugins to monitor logs but it did not work for me.

For how long have I used the solution?

I have been using this solution for one and a half years.

What do I think about the stability of the solution?

This solution is stable. It does not consume a lot of memory and the networking is fine.

We have not had any issues with the CPU, memory, or network.

It's compatible with the old machines with old platforms. It is not, however, compatible with all of the tools, but it's fine.

There are different machines and different environments with over five hundred nodes that have different structures.

What do I think about the scalability of the solution?

This solution is scalable. 

You can scale by opening an RP file or configuration file, add your plugin, and monitor, then reload the configurations.

During the implementation, I added the automatic plugin with ansibles and Icinga. When you run the ansible file, it implements the automatics, it then reloads the plugin for you, no manual work is needed.

How are customer service and technical support?

I have not contacted technical support.

How was the initial setup?

The initial setup was easy and straightforward, but the implementation was not as easy as it was perceived.

What about the implementation team?

We deployed Icinga and the event handler through our IT services.

What's my experience with pricing, setup cost, and licensing?

This is an open-source solution with paid support.

What other advice do I have?

 I would rate this solution an eight out of ten.

**Disclosure: I am a real user, and this review is based on my own experience and opinions.
More Icinga reviews from users
...who compared it with Nagios Core
Add a Comment