Icinga Reviews

Ability to integrate the various custom metrics & reporting tool which supports multiple monitoring aspects. I have used Memory, CPU, and Disk IO metrics to be shown in Icinga.

Alerting system is something that I couldn't find in the version I have used, perhaps Alerting could be a great add-on capability such as Mail notifications & PagerDuty alerts etc.

By integrating a central Icinga platform, we can easily show all our Application Servers in a single interface so that we do not have to worry about the application's respective owners constantly monitoring the metrics. Have a big Monitor in Workspace & open this application there & have more extensive visibility in office.

Icinga2 is open-source, so the costs are manageable, and the product itself is permanent in development. If something's going wrong or there are failures, it's no problem to reach the developers.

It's very reliable; we are a huge company (Gouvernement) and need reliable solutions. With two icinga2 hosts, we can manage over 44000 Services and 3500 Hosts.

It uses the same checks as Nagios; if a service-check isn't available, it's easy to write one.

Our admins could write checks, too. They use bash, PowerShell, Perl.. or whatever for scripting; it doesn't matter. With the windows agent, we can use PowerShell checks, with Linux agents bash or similarly.

It's not very much I dislike. Sometimes i feel we could have better modules for icingaweb2, but it's not the blame of the Icinga-developers. Sometimes we have to sponsor when we need functionalities, but it's opensource!

With other solutions, we've had those problems:

- we haven't enough licenses for the number of hosts, Icinga doesn't need Licenses, but you could make a contract for support with Icinga partners.

- we have had many stability problems with other products, no problem with icinga2

- we had to pay very much for extensions (for example, MySQL monitoring) with other solutions in the past. Now we write it or use monitoring plugins from Icinga, consol-labs,...and so on.

With Icinga we are working with our admins; we can monitor what they want.

Easy configuration using files. No UI. So it can be automated by any provisioning software(puppet, ansible, chef)

Outdated UI compared to competitors. Not frequent updates. Lack of extensions.

Distributed monitoring of services and servers. Time-based notifications.

The dashboard is very user-friendly, you can see alerts for services, ceased alerts, and alerts for hosts. Also, black skin is great.

When you click on alert history it is a little bit untransparent, also it will be great to make one dashlet for acknowledged alerts separately.

I'm monitoring Linux servers and services, also windows server and services, databases, network... A great benefit for quick solving issues.

I've worked with Icinga in multiple organizations, spanning thousands of devices. I love the configurability of the Icinga framework, although for admins new to the platform it may seem intimidating to edit the config files.

Icinga2 brings additional features that help automate and configure with less flat file configuration needed but neither product should be brought in lightly. They both require a lot of work up front to be tuned in such a way as to provide benefit that can be mapped back to business requirements. Fortunately, there is a plethora of documentation available as they are widely used.

The flat files can be intimidating, and the web interface plugin is not very intuitive. Easy to script and automate, however.

Icinga has helped my team identify problems in our infrastructure early on so as to remediate before the issue escalates. It also helps provide insight into the root cause of an outage as you can best and map devices to logically show flow.

La gran cantidad de plugins/modulos que soporta, la cantidad de sistemas que puede integrar para su monitorizacion:

* Redes

* Componentes de red

* Notificaciones

* Niveles de alerta

* Interfaces

La gran cantidad de mejoras que tiene con respecto a Nagios, y la compatibilidad con sus módulos.

Algunas alarmas pueden tener un delay, segun lo grande que se el sistema de monitorizacion, y pueden dar falsos positivos, aunque en nagios pasa exactamente lo mismo, no llega ser un 100% a tiempo a real si no un 90% o 95%.

La gran cantidad de vistas que ofrece, aveces puede ser una desventaja mas que una ventaja, ya que en unas te pueden aparecer unas alarmas y en otras otra...

Si tienes Nagios, yo migraría hacia Icinga por varias cuestiones, pero las mas destacables son su completa gratuidad, la gran comunidad open source que tiene detrás en un continuo desarrollo de la aplicación, y el gran soporte que tiene gracias a esta comunidad de usuarios y desarrolladores. Ademas la cantidad de módulos que tiene es infinita permitiéndote chequear gran cantidad de sistemas, redes, temperaturas de congeladores o estufas etc.

La utilizamos para monitorizar las redes y los equipos frigoríficos de la organización, con un alto rendimiento de monitorizacion, llegando a tener cientos de dispositivos monitorizados,

La gran cantidad de plugins/modulos que soporta, la cantidad de sistemas que puede integrar para su monitorizacion:

* Redes

* Componentes de red

* Notificaciones

* Niveles de alerta

* Interfaces

La gran cantidad de mejoras que tiene con respecto a Nagios, y la compatibilidad con sus módulos.

Algunas alarmas pueden tener un delay, segun lo grande que se el sistema de monitorizacion, y pueden dar falsos positivos, aunque en nagios pasa exactamente lo mismo, no llega ser un 100% a tiempo a real si no un 90% o 95%.

La gran cantidad de vistas que ofrece, aveces puede ser una desventaja mas que una ventaja, ya que en unas te pueden aparecer unas alarmas y en otras otra...

Recommendations to others considering the product:

What problems are you solving with the product? What benefits have you realized?

1) Powerful Infrastructure Monitoring engine for On-Premise and SaaS-based Cloud Applications.

2) Excellent Analytical capabilities to identify trending patterns for reporting and insights.

3) Customized Notifications and integration to outbound platforms like Slack, ServiceNow etc., for quick actions.

4) Great Community Support.

1) Improvements are needed on the User Interface part.

2) You need to be a command line user for faster installation.

3) Documentation needs a little advancement to resolve problems quicker.

1) It is an ultimate monitoring tool. We get underlying information about the processes, daemons, and services which helps us to determine the issue proactively to take action before user initiated triage.

2) Icinga has great Activa and Passive Checks functionality, which makes NOC life easier.

It is open source and free, meaning the software is easily extendible. All Nagios plugins, as well as all the community plugins are usable with Icinga. You can use alot of advanced features, including check scheduling, notification escalation or a very detailed user access and management system. It is very easy to extend the system with extra checks or hosts due to the templating system.

The setup of the software can be quite complicated depending on the OS you are deploying on (I deployed on Alpine Linux) and the documentation for this is not complete. After setup, the initial learning curve is quite steep and takes quite some time. For instance, you need to create a notification template to create a notification object to create a user template to create a user, etc.

Do a small pilot before trying to add too much at once. Also consider adding meta-tags to objects, so you can use these to define conditionals.

We use Icinga as our monitoring system for each of our 25+ servers. It performs manual and automated checking and notification of abnormalities. The performance data generated by these checks are stored and visualized in Grafana dashboards for business insight.

It is very flexible to monitoring of services and the speed,It has a rich configuration language that allows expression of complex configurations in a minimal amount of text, allowing monitoring configurations to be written quickly and concisely

It would be appreciated if there is a good support

I worked on a NOC project where we used Icinga for monitoring the linux servers to make sure all the services are working and to overcome the system downtime.