Icinga Infrastructure Monitoring Reviews & Product Details

What I appreciate most about Icinga is the flexibility it offers, especially when managing monitoring across a large and distributed infrastructure. I've been working with Icinga for several years, from our migration from Icinga 1 to Icinga 2 to managing and improving the platform in our day-to-day operations.

At Giesecke+Devrient, we use Icinga to monitor around 4,500 systems and over 48,000 services across more than 80 locations worldwide. We have a distributed setup with redundant masters and satellites, which allows us to monitor infrastructure across different sites and network zones while maintaining a central view of the environment. In my experience, Icinga handles this scale well when the architecture is properly designed.

One of the things I value most is how easily we can integrate it with our existing automation. We've automated monitoring deployment, onboarding and decommissioning through AWX and our infrastructure workflows, so adding or removing servers doesn't require the same manual effort it used to. The API and configuration flexibility have been particularly useful here.

We also monitor a wide range of technologies, including Linux, Windows, VMware, network devices, databases and applications. Being able to use existing plugins or develop our own checks for specific requirements is a major advantage. Icinga Web 2 gives us the visibility we need for daily monitoring, troubleshooting and handling alerts.

Overall, Icinga has given us a reliable and highly customizable monitoring platform without the licensing restrictions of many commercial solutions. It takes experience and effort to operate at this scale, but the flexibility and control it provides are the main reasons I value it. Review collected by and hosted on G2.com.

One area I feel could be improved is how Icinga handles monitoring workloads during satellite maintenance or failover, particularly in large environments.

We have locations where a satellite pair is responsible for monitoring close to 1,000 hosts and several thousand services. When one satellite is taken down for patching or maintenance, the remaining satellite has to handle the monitoring workload. This can lead to sudden spikes in check execution and resource utilization, especially when a large number of checks are scheduled around the same time.

Because of this, we have to plan satellite maintenance carefully to avoid overloading the remaining node. Better workload distribution and smoother handling of check execution during failover would make a real difference in larger deployments.

Another area I'd like to see improved is the dashboard experience in Icinga Web 2. While users can create their own filtered views, having centrally managed dashboards that can be shared with teams or made available to all users would be much more practical. In a global environment like ours, it would help us provide consistent monitoring views without everyone having to configure their own filters.

Overall, Icinga works well for our requirements, but improvements in these areas would make day-to-day operations easier, especially for teams managing large distributed environments. Review collected by and hosted on G2.com.

The ease of implementation and extension, for many years I have used Icinga as the core for all internal infrastructure monitoring and for my clients. Not only using the base but extending it by creating modules and plugins tailored to needs, also integrating other open-source tools like Nagvis, Report Server, OCS Inventory, OTRS/Otobo, and many more. Especially useful for deploying monitoring via SNMP and Databases where I can create my own monitoring. Being open-source software, I don't need to invest my money in licensing or paying for other products, I manage to meet most of my needs in a single tool that also allows me to scale capabilities by adding agents and satellites when necessary. Also, always using the multiple versions of open-source operating systems like Redhat, CentOS, Alma, Linux. Review collected by and hosted on G2.com.

What I don't like is that it has fallen behind in recent years regarding the observability boom. I would expect more momentum in generating a single point for collecting trace metrics and logs, as other tools that started in the monitoring area have expanded their horizons. Review collected by and hosted on G2.com.

The main features of Icinga include the exceptional ability to customize checks, allowing targeted monitoring of virtually any service through custom-developed scripts. Icinga's interface is quite complex and requires thorough study to fully exploit its various functionalities; at the same time, however, it is very flexible and versatile. Icinga easily integrates with external systems for sending alerts, for example via email or Slack. The product is open-source and has a low adoption cost, with an excellent cost/utility ratio. Moreover, it does not require significant computing resources: except in cases of monitoring complex systems, performance is excellent. There are no AI features. Review collected by and hosted on G2.com.

The interface is sometimes quite complex and not always intuitive: even for simple operations, it may be necessary to configure many fields, making the process more cumbersome than expected. Review collected by and hosted on G2.com.

We are a managed service provider and have been running Icinga 2 for more than five years. It monitors our own infrastructure and our customers’ environments, between 100 and 500 hosts in total. The distributed architecture is the main reason we stay with it. Each customer environment gets its own satellite zone, so we keep tenants cleanly separated and still see everything in one central place. Icinga Director is the second big win: host templates, service sets and baskets let us roll out a consistent monitoring standard instead of writing config by hand. The plugin ecosystem is very flexible. Because it is Nagios-compatible, we can combine community plugins such as the Linuxfabrik Monitoring Plugins with our own checks. And since it is open source with no per-host licensing, costs don’t grow every time we onboard a new customer. Review collected by and hosted on G2.com.

Maintaining Icinga for Windows takes more effort than I would like. Updating the framework across many Windows servers requires care, for example rebuilding the code cache and restarting the service, and newer Windows Server versions such as 2025 needed adjustments to our check commands. We ended up writing our own deployment script to keep agent rollouts consistent. It works well now, but a more streamlined update path would help. Like any distributed monitoring setup, Icinga also takes some time to understand at the beginning: zones, endpoints and config sync need a solid concept. Review collected by and hosted on G2.com.

Icinga is simple and built upon a few concepts only. It lets you define your exact monitoring strategy using WebUI or files. After years of usage, it has not failed me. It does the job every day and lets you add the bells and whistles you want. Being open-source is key, you don't want to give your precious to a black box. Review collected by and hosted on G2.com.

Not that much! I have not seen lots of revolutions with Icinga within all the years we've been using it. That could be a bit boring, but the key here is reliability, not the wow effect! Review collected by and hosted on G2.com.

Its very customizable and adaptable. Everyting I want to edit can be added, changed or replaced. Due to the opensource nature and large nagios & icinga community, lots of integrations already exist. Review collected by and hosted on G2.com.

The learning curve can be steep, especially for new, empty environments. There are many ways how icinga can be configured, and if you too much about inheritance and structure you can get a bit stuck at first Review collected by and hosted on G2.com.

Integration

I particularly like the flexibility of Icinga to develop and integrate custom plugins to optimally adapt monitoring to specific requirements. Especially the ability to use custom scripts, for example in Bash, for individual monitoring checks offers great freedom and allows specific use cases to be covered easily.

UI

I particularly like the ability to centrally and flexibly configure monitoring via the Icinga Director and Icinga Web 2. However, there are still occasional minor bugs that slightly impair the user experience.

Performance

Icinga is one of the most stable monitoring solutions we use in our environment. I have used the tool in different environments and have always been satisfied with the performance and reliability.

Pricing

A major advantage of Icinga for me is the open-source approach. This makes the solution particularly interesting for companies that want to implement powerful and flexible monitoring without high licensing costs. I cannot provide a well-founded assessment of the costs of possible support contracts due to lack of insight.

Support

My experiences with NETWAYS support have been consistently positive. Inquiries were always answered promptly. The contacts were professionally competent and could provide targeted and well-founded assistance with the respective issues.

AI

I am currently not aware of any AI functions that I actively use. Therefore, I cannot currently provide a well-founded evaluation of this aspect. Review collected by and hosted on G2.com.

In the Icinga Director, there are occasional minor bugs and UX issues that unnecessarily complicate daily work. For example, when creating commands, after clicking "Add," the input fields of the last added argument remain filled. If you add an argument again after a change, the existing one is overwritten instead of creating a new one. Such small issues occur in several places and impair the ease of use.

Another point of criticism is the lack of an integrated way to comfortably evaluate historical performance data and long-term trends. Icinga reliably monitors states and alerts when thresholds are exceeded, but offers only limited options for long-term analysis, for example, for network traffic or RAM usage. An additional solution like Grafana is usually required for this. Therefore, a more integrated visualization and trend analysis would be a useful addition.

Another improvement point for me is the flexibility of the Director API. Especially in the management of service sets and the assignment of services, more comprehensive API support would be desirable. In general, a more consistent and complete API would significantly facilitate automation and integration into existing systems. Review collected by and hosted on G2.com.

It's flexibility. The product is very mature and very easy to extend. We monitor a wide range of applications and systems that all have their unique challenges when it comes to monitoring. Icinga's flexibility in terms of writing custom scripts that provide structured input into its pipeline is a lifesaver. The UI is easy to understand and flexible enough to use in different scenarios and on different devices. Review collected by and hosted on G2.com.

The setup, especially when it comes to clustering, high availability and resilience, is very complicated and the documentation while present feels lacking in that regard. The breadth of official add-ons to the product is great but I find the management of updates and new releases lacking. Review collected by and hosted on G2.com.

What I like most about Icinga Infrastructure Monitoring is its versatility: I can adapt it to very small needs or huge infrastructures, and use it in different contexts. It allows me to gather monitoring of networks, servers, applications, and databases, and generate the corresponding alerts. Moreover, it is free software, which is fundamental for me: I can offer it without hidden licensing costs and, if I need special customization, I can edit the source code. I like that it continues to adapt and evolve, and that it has a large community that guarantees long-term support. For most basic infrastructure monitoring needs, it seems to me an excellent, open, and cost-effective solution. Review collected by and hosted on G2.com.

Icinga has fallen behind in observability: other solutions already incorporate trace and log monitoring, while in Icinga you have to do everything manually, which is a bit more complicated nowadays. I also think it should incorporate artificial intelligence elements. Configuring it is not easy and has a significant installation gap, although this is an expected difficulty in a specialized monitoring tool. Review collected by and hosted on G2.com.

What I like most about Icinga is how flexible it is. Any script or plugin that returns a status can be used as a check, so almost any system, device or service can be monitored. The distributed architecture scales well and still gives one central view of the whole environment. Templates and rule-based configuration make it easy to roll out monitoring to many hosts at once without setting up each one by hand. The API also makes it easy to connect Icinga to other tools like ticketing, dashboards or automation. Review collected by and hosted on G2.com.

https://github.com/Icinga/icingadb-web/issues/1407

:-( Review collected by and hosted on G2.com.