Blog

Monthly Snap April: Berlin Meetup, Releases and Themes

April brought us new bugfix releases of Icinga 2 v2.8 and Icinga Web v2.5. Carsten released new versions for the Grafana module for Icinga Web 2. Christoph updated everything to the latest in his Docker containers.

Blerim wrote a thing about continuous monitoring on the Chef blog. The Icinga 2 master instances in NWS now provide the possibility to send Slack notifications. Jens shared insights into pushover notifications. Assaf is working on the Ansible playbooks and gives a peek in to Terraform. Emil released a new version of the check_domain_expiration plugin.

Our community channels brought more insights into Icinga Web 2 and custom service grids, and Icinga 2 with custom filter functions for apply for rules.

Simon and Nicolai created the first Icinga meetup in Berlin on May 16th 2018 – make sure to join them!

read 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.

Monthly Snap March: Icinga Camps, Roadmap & Releases

Icinga Camp Berlin and New York were a blast – thank you everyone for joining! The archive for both is now online including slides and recordings. Marianne shared her impressions and Marco did so too :)

We’ve also had the pleasure to join the 2nd Icinga meetup in Zurich. Oh what a lovely community … we’ll sure be back for more #icingalove ❤️

We’re already planning for Berlin 2019 and would love to see your talks on how you use Icinga, integrations, cool new ideas, or just the crazy things no-one expects … did I say LSD theme? Want your own Icinga meetup in your hometown? Just get in touch, we’ll help you organise and can provide some swag too.

read more…

Icinga 2.8.2 released

Today we release Version Icinga 2.8.2, a bugfix release with a focus on security. Most of these have been brought to our attention by the community and we are very thankful for that. Special thanks to Michael H., Julian and Michael O., who helped by reporting and assisting us in fixing security bugs. CVEs have also been requested for these issues, they are as follows: CVE-2017-16933, CVE-2018-6532, CVE-2018-6533, CVE-2018-6534, CVE-2018-6535, CVE-2018-6536. The full advisory from Michaels point of view can be found on his website.

As a side effect of these fixes a few things need to be considered during the upgrade:
For one, the init.conf is gone. Everything that used to be configured in there, ie. Icinga user, Icinga group and resource limits, are now found in the sysconfig file (usually /etc/sysconfig/icinga2). This means if you did manually edit init.conf, to change the user icinga 2 runs as for example, you will have to move these changes to the sysconfig. See the documentation for details. Secondly we added the cli command icinga2 api user which can be used to create ApiUser object configuration with hashed password strings.

If you did not change anything in init.conf, all of this is optional and additive and the upgrade path is safe.

Additional changes and details can be found in the changelog.

Updating is strongly recommended. We are striving to make Icinga 2 as secure as possible, to that end we created a security mailbox for you to send us security reports and vulnerability information. We support the responsible disclosure of vulnerabilities and therefore ask for sufficient time to patch the issue before publishing the details.

Official packages are available on packages.icinga.com. Community repositories might need a while to catch up.