Icinga 2 v2.9 introduced performance related changes inside the configuration compilation and activation order. This was to ensure a) no unwanted notifications b) use available CPU resources to speed up the overall validation process. These changes had a bad effect on configuration depending on a specific activation order, and slowed it down with many config objects of a specific type. The Icinga Director depends on get_host() being called in service objects to support specific service set overrides.

Under the hood, Icinga 2 uses many constants and reserved keywords, e.g. “Critical” or “Zone” which are respected by the config parser and compiler. This sometimes leads to errors when users accidentally override such things, or re-define their own global constants. v2.10 introduces namespaces for this purpose, and ensures that such accidents won’t happen anymore.

Our first Icinga Camp Tel Aviv happens on December 17th, 2018, the fourth edition in Berlin takes place on March 14th, 2019 again :) The first Icinga meetup in Salzburg, Austria happens on Oct 12th, 2018 – join for more #icingalove. The Berlin meetup was a great success, Carsten and Lennart joined there too. Watch their meetup group for future dates.