Being able to have masters and satellites

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.

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.