Icinga Infrastructure Monitoring Reviews & Product Details

I use Icinga to monitor my entire infrastructure – from Proxmox and vSphere to SAN and the Internet, down to small services. I appreciate the flexibility and simplicity. Icinga is continuously developed and has an active community. I like the further developments, such as IcingaDB and IcingaX509. Icinga Director is one of the best things about Icinga for me and offers many automation features. I also appreciate that I can automatically provision hosts and agents. A new Proxmox host is automatically assigned the appropriate service sets based on its note and receives both Proxmox and Linux checks via the standardized Linux agent. With Ansible modules, I can implement the installation easily and fully automatically. I don't have to work in config files, and Icinga is not as memory-hungry as Nagios. Moreover, I can rely on Icinga to automatically notify me when a problem occurs – it lets me sleep peacefully. Review collected by and hosted on G2.com.

The installation was difficult for me because the documentation was not straightforward. The documentation for new installations and updates could be clearer and is not always entirely understandable, especially since PostgreSQL and MySQL are often mixed. However, a lot has improved in the documentation recently. Review collected by and hosted on G2.com.

What I like most about Icinga is its flexibility. If something exposes a sensor, metric, command output or other form of data, I can find a way to monitor it, regardless of what it is or where it is located.

I use Icinga to monitor around 10,000 hosts and 50,000 services across hundreds of remote sites. Its flexibility and scalability allow us to operate a distributed monitoring platform with centralised visibility across diverse environments, technologies and customer sites.

Icinga also integrates well with other open-source tools, including Grafana and InfluxDB. This allows us to combine infrastructure monitoring with time-series data, dashboards and historical performance analysis, extending the value of the platform beyond alerting and service availability.

The cost savings are significant. Comparable commercial monitoring solutions could cost close to $50,000 per year for a non-redundant deployment, or $100,000 per year for a redundant environment. By building our platform entirely on open-source software, we have achieved this scale and resilience without software licensing costs or significant upfront software investment.

The ability to monitor almost anything, extend functionality through custom checks, integrate with other tools and distribute monitoring across hundreds of sites makes Icinga a powerful and cost-effective alternative to expensive proprietary solutions. Review collected by and hosted on G2.com.

There is a steep learning curve, and the flexibility sometimes comes with the tradeoff that it is hard to determine what is best practice. Review collected by and hosted on G2.com.

What I love most about Icinga Infrastructure Monitoring is its flexibility and adaptability. Being open-source, I can customize checks and develop my own plugins and modules to monitor specific components that standard checks don't always cover, such as Oracle and MSSQL databases, WebLogic logs, DB2 queries for IBM iSeries, and telecommunications equipment via SNMP. I can also integrate different technologies according to the needs of each environment and rely on Claude Code to create custom modules and explore ways to expand Icinga. This way, I can adapt the tool to the real requirements of my infrastructure, rather than adjusting the infrastructure to the limitations of a tool. Icinga also helps me detect failures, performance degradation, or unavailability in time. The transition from Nagios was quite natural due to the similarities and compatibility. Review collected by and hosted on G2.com.

I would like Icinga Infrastructure Monitoring to evolve towards a more comprehensive observability platform, with native intelligent analysis capabilities. It would be very valuable if it could analyze historical trends, correlate metrics and events, identify anomalous patterns, and help determine the root cause of incidents. Currently, to have these capabilities, I need to integrate external tools or develop custom solutions. Review collected by and hosted on G2.com.

What I like best about Icinga Infrastructure Monitoring is its flexibility and the level of visibility it provides across infrastructure. The interface offers a clear overview of monitored systems, and its dashboards and alerts make it easier to spot issues and investigate them. Icinga integrates well with a wide range of tools and technologies, which is especially useful in environments with mixed infrastructure. Performance has been reliable for our monitoring needs, and the open-source option can offer strong value, although setup and maintenance require time and technical expertise. The documentation and community resources are helpful, but onboarding can take some effort for new users. Icinga’s strengths are primarily in monitoring, alerting, and automation rather than AI-driven analysis. Overall, it’s a flexible and capable solution for teams that want control over how their monitoring is configured. Review collected by and hosted on G2.com.

The main downside of Icinga Infrastructure Monitoring is that it can take time and technical expertise to set up, configure, and maintain, particularly in larger or more complex environments. Some tasks may require working with configuration files, and the interface can feel less intuitive for new users than simpler monitoring tools. Integrations are flexible, but configuring them may involve additional effort. Review collected by and hosted on G2.com.

I appreciate the reliability and expandability of Icinga Infrastructure Monitoring as well as the integration with other applications. The setup can be easily expanded with satellites and agents, and I can easily add my own checks. I particularly like the integration via the Netbox plugin because Icinga is largely stateless as a result. Review collected by and hosted on G2.com.

I find the automation in Icinga for Windows confusing. Setting up imports and syncs along with assigning them to templates with Icinga Director is relatively cumbersome. Dashboard sharing would also be helpful. Review collected by and hosted on G2.com.

The possibilities for automation, e.g. using the Icinga (Director) API to automate service registration. I also like the newly added Icinga for Kubernetes integration as a general overview of Kubernetes components health. Review collected by and hosted on G2.com.

I think the UI could use a fresher and cleaner look. It's a bit overwhelming and not super beginner friendly if you onboard new colleagues for example. Review collected by and hosted on G2.com.

Quick visibility of actual and potential issues, which helps us maintain our customer systems. The notifications help alter other team members to issues and allow speedy remediation. Review collected by and hosted on G2.com.

Very difficult to monitor container-based systems. The Kubernetes monitoring seems to work well, but not so much when dealing with Docker deployments on ECS. Review collected by and hosted on G2.com.

I find Icinga Infrastructure Monitoring well configurable and can monitor basically everything I want, and scale my environment well. The simple configuration ensures quick deployment, and I can quickly train colleagues in its operation. With the plugins, especially the Director, Icinga is also easier to use for colleagues who are not so CLI-savvy. The community is helpful and constructive and always strives for further development. If there are problems, the documentation or the community helps me. I also like the modern design and the very simple initial setup. Review collected by and hosted on G2.com.

Currently, I can't think of anything I don't like about Icinga Infrastructure Monitoring. Review collected by and hosted on G2.com.

I like that Icinga Infrastructure Monitoring is very flexible. Its framework lets us build and customize monitoring to our needs, integrate other monitoring and specialty systems, and mirror their states in Icinga. The web modules are flexible, and the domain-specific language lets us customize monitoring computations, including combining cluster-node data into an overall state. The vSphere DB module lets us get data from our virtualization environment, and the business process module helps us gather information together and create a high-level view of the data. Flexibility and cost were reasons we switched from CA Spectrum. Review collected by and hosted on G2.com.

The rough edges of the web modules, especially the navigation between them. For example, when I build a service check on a host based on virtual machine state from the vSphere DB module, there's no automatic linking between the objects so that a user can jump from one module to the other and stay in the object context. Since Icinga Infrastructure Monitoring is like a framework or a tool box, setup can feel like starring at a white canvas or a big box of Lego without the build guides. Because of this we used a consultant to build our solution and make sure we stayed within best practices. Review collected by and hosted on G2.com.

I like Icinga Infrastructure Monitoring’s modularity and compatibility with open source. I have a lot of different technologies running and not much budget for software, so I can write a script and use it as a service check. I can monitor anything I can see with a script, including through my Prometheus and healthchecks.io integrations. Review collected by and hosted on G2.com.

I find setup confusing, and the documentation is sparse at times or nonexistent. I have to trial and error my way through sometimes, and I frequently can’t find cookbook instructions for new features. I still haven’t gotten the new Notifications module running. When I rebuilt from scratch, I also had to figure out database setup and how to configure modules I didn’t know, which took a deep RTFM dive. Review collected by and hosted on G2.com.