Icinga 2 DSL Feature: Namespaces coming in v2.10

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.

 

What exactly is a namespace?

Think of a defined “room” for variables, functions, etc. which can be defined similar to constants. They are isolated from other namespaces and must be loaded by the user/developer. Namespaces need a defined name – we prefer to use a capitalized string, e.g. “MyNamespace”. This helps to immediately qualify this as customization when reading the configuration.

Icinga 2 v2.10 uses namespaces which are registered and loaded by default. In order to test this, open the debug console on a test VM which has the snapshot packages installed. Fetch the keys in global namespace “globals” first.

(more…)

Icinga 2.9.1 released

Icinga 2.9.0 provided many many bugfixes and one change has unfortunately been overseen. If you use an init system different to Systemd (e.g. Sysvinit) or the “-d/–daemonize” option in your containers, issue #6445 causes troubles. This is visible with logging, cluster connects, IDO database writing. Users reported problems on CentOS 6, SLES 11, Ubuntu 14, Debian 8, Gentoo (both with Sysvinit).

Thanks to the quality feedback from community members and contributors, we’ve analysed and fixed the problem last week. Next to that, Dirk has updated the SELinux policy to allow Systemd notifies, and another fix deals with init script sourcing on non-posix systems.

Release packages for v2.9.1 are available on https://packages.icinga.com. Linux/Unix masters, satellites, clients require the update, Windows clients are not affected.

Icinga 2.9.0 released

This release comes with Elasticsearch 6 support sponsored by a customer – cheers to Vienna! In addition to this feature, we’ve also taken care of unwanted unknown results on reload with command endpoint clients. Thanks for sponsoring a long lasting issue fix.

v2.9.0 contains many bugfixes and improvements requested by Icinga partners and their customers. Our community members have also been reporting and testing quite a bit, especially the nasty bugs with memory leaks on REST API requests are fully resolved.

Thanks to all contributors: Magnus, CarstenMax, Leah, Adam, Akrus, Jorge, Andrea, terra-nova, Maurice, Michal, sahnd, Kami, Federico, Harald, Fabian, Lee for your awesome work!

(more…)

5 Benefits of integrating OpsGenie and Icinga2 for better incident management

5 Benefits of integrating OpsGenie and Icinga2 for better incident management

Icinga2 is an open source IT infrastructure monitoring tool that shines with its performant and highly configurable monitoring solution. It has built-in notification scripts such as e-mail, SMS, and Twitter to send notifications when an alert is triggered. These scripts, combined with configuration files, give you basic alerting capabilities such as notifying a team. Often teams need more advanced workflows and alerting needs.

In this blog post, you’ll learn five different ways OpsGenie helps Icinga users. Before starting, let’s talk a little bit about OpsGenie. (more…)

Icinga 2.8.3 released

Today we are releasing a new support version of Icinga 2.8, a small one to pass the time until 2.9. This release includes fixes for the InfluxDB and Elasticsearch features. Please note that Elasticsearch 6 support is coming with 2.9. In addition to the fixes we’ve added support for multiple check parameters for the check_nscp_api plugin and working sysconfig/defaults variables support, you’ll also find many documentation updates. For this release you don’t need to follow any special upgrade procedure, upgrading is safe.

Additional changes and details can be found in the changelog.

As always official packages are available on packages.icinga.com while community repositories might need a bit to catch up.

Update 2018-04-25 16:45 CEST: Users reported problems from a regression. We have therefore released v2.8.4.