Talk:Icinga

=== Oracle not supported for IDO database === The IDO database is not actually supported on Oracle -- this is a historical artifact.

WilliamsJD (talk) 15:41, 16 September 2020 (UTC)

Current version describes old 2018 architecture. Update suggested.

Hi, I work at Icinga (want to disclose this upfront). The current version of the article describes an old version of Icinga 1.x, which has been superseded and no longer reflects how the software works today. Icinga 2.x exists since 2014. Source: https://github.com/Icinga/icinga2/releases/tag/v2.0.0

I completely understand AI clean up efforts in general. My concern is only the technical accuracy of the current content. I list the points below with official sources from Icinga documentation, so that anyone can verify them independently:

1) Stable release: The article says latest release version = 2.15.0 (Icinga 2). The latest release version is 2.16.4. Source: https://github.com/Icinga/icinga2/releases

2) Core language: The article says the core is written in C. The Icinga 2 core is written in C++. Source: https://github.com/Icinga/icinga2

3) Icinga Core / IDODB / IDOMOD / IDO2DB: The article presents the IDO database as the current architecture. The IDO feature is deprecated and scheduled for removal in v2.18; it has been superseded by Icinga DB. Sources: https://icinga.com/docs/icinga-2/latest/doc/14-features/ (marked "DEPRECATED and will be removed in v2.18") and the official migration guide https://icinga.com/docs/icinga-db/latest/doc/06-Migration/

4) Doctrine abstraction layer: This applied to Icinga Web 1.x / Classic UI. It is no longer used since Icinga Web 2. Source: https://icinga.com/docs/icinga-web/latest/

5) Windows monitoring via NSClient++/Cygwin: The old Windows check-plugins are deprecated; the docs now point to native PowerShell plugins. Source: https://icinga.com/docs/icinga-2/latest/doc/16-upgrading-icinga-2/

6) Icinga Mobile: This is no longer part of the product line. It's not listed in the current product overview: https://icinga.com/products/

7) Icinga Classic UI: Superseded by Icinga Web 2. Source: https://icinga.com/docs/icinga-web/latest/

8) Comparison: Other open-source infrastructure monitoring tools operating in the same landscape include: Nagios, Zabbix and Checkmk.

For context, the version from 11 June 2026 was sourced and technically accurate for most of these points, even though it still described IDO rather than Icinga DB.

Would it make sense to restore that version and then update the Icinga Core section to reflect Icinga DB? Happy to provide sources for any further detail, but given my COI I would like to leave the actual editing to the community.

Thanks for looking into this. So1289 (talk) 10:27, 21 July 2026 (UTC)

I'll try that approach and see how it goes; otherwise I can re-revert and then fill in the missing info. Please be patient with messy intermediate steps! M kuhner (talk) 02:46, 23 July 2026 (UTC)

Okay, some questions:

(1) How do I get the date of release 2.16.4? The github page says "last week" which is not too helpful.

(2) Can you provide a source for "frontend PHP"? The given source does not mention that anywhere I can see.

(3) The statement in this version: Icinga 1.x maintained compatibility with Nagios plugins and configuration files, adding a modern web interface, additional database backends (PostgreSQL, Oracle), and a REST API. are sourced to which is apparently an LLM hallucination as the source does not cover those topics.

(4) The reference {{cite news |last=Henning |first=Edward |title=Nagios fork Icinga 1.6 records SLA information |url=http://www.h-online.com/open/news/item/Nagios-fork-Icinga-1-6-records-SLA-information-1390710.html |work=The H Open |date=December 6, 2011}} goes to the landing page of the publication and does not find the article.

(5) Icinga 2.0 was released in June 2014 with a new domain-specific configuration language, a built-in TLS-secured cluster stack for distributed and high-availability setups, and a REST API for external integrations. is sourced to "Icinga 2.0 has arrived" which fails to confirm most of it.

This text is rotten with LLM hallucinations. Probably looks okay to you because things are more or less factual...but all the claims of support from the sources are NOT.

At this point I am giving up on rescuing the LLM edit. I will back out and try to insert changes by hand instead, because nothing here can be trusted and it's hard to keep straight. M kuhner (talk) 03:29, 23 July 2026 (UTC) M kuhner (talk) 03:29, 23 July 2026 (UTC)

It's an awful mess. Just touching or moving some of the references trips the edit filter (they are using a deprecated archive site with malware). It's going to take a careful full rewrite which I cannot do tonight. Both the older version and the LLM newer version are bad in excitingly different ways; and, alas, the older version is probably ALSO LLM.

I will work on this later this week. So1289, if you could identify replacement sources for some of the dead ones in the current version of the article and post them here, that would be incredibly helpful. I can't source claims of features to bare Github sites. At minimum I need Icinga saying these features exist; much better, a secondary source saying the same. M kuhner (talk) 04:58, 23 July 2026 (UTC)

(1) How do I get the date of release 2.16.4? The github page says "last week" which is not too helpful.

On our GitHub releases you can click the little verified tick for the tag, which gives you a timestamp, instead of the more readable format GitHub chooses for the releases.

(2) Can you provide a source for "frontend PHP"? The given source does not mention that anywhere I can see.

That would be https://github.com/Icinga/icingaweb2 under "languages". As secondary source you can use https://icinga.com/docs/icinga-web/latest/doc/02-Installation/ as PHP ist mentioned as prerequisite.

(3) The statement in this version: Icinga 1.x maintained compatibility with Nagios plugins and configuration files, adding a modern web interface, additional database backends (PostgreSQL, Oracle), and a REST API. are sourced to which is apparently an LLM hallucination as the source does not cover those topics.

Icinga 1.x is relevant only for historical purposes, at most, because it has not been supported since 2014. This makes it difficult to find suitable sources that haven't already been deleted.

(4) The reference {{cite news |last=Henning |first=Edward |title=Nagios fork Icinga 1.6 records SLA information |url=http://www.h-online.com/open/news/item/Nagios-fork-Icinga-1-6-records-SLA-information-1390710.html |work=The H Open |date=December 6, 2011}} goes to the landing page of the publication and does not find the article.

It looks like Heise cleaned up their blog. Not sure if the web archive is a suitable source, but there you can still find the article: https://web.archive.org/web/20240213182617/http://www.h-online.com/open/news/item/Nagios-fork-Icinga-1-6-records-SLA-information-1390710.html

(5) Icinga 2.0 was released in June 2014 with a new domain-specific configuration language, a built-in TLS-secured cluster stack for distributed and high-availability setups, and a REST API for external integrations. is sourced to "Icinga 2.0 has arrived" which fails to confirm most of it.

The official release notes here should be more suitable than the blogpost: https://icinga.com/docs/icinga-2/latest/CHANGELOG/#200-2014-06-16

Hope this helps! So1289 (talk) 07:33, 27 July 2026 (UTC)