Today we’re announcing the general availability of Icinga DB Web v1.1.1 and Icinga Web 2.12.1.
Icinga DB Web
You can find all issues related to this release on our Roadmap.
Automated Migration
The release of v1.0.0 already assisted in migrating URLs from the monitoring module to Icinga DB Web. Though, it was still rather cumbersome to use and no option for large installations. And to be honest, it also wasn’t made with migration in mind. The actual intent was to encourage checking Icinga DB Web out, while the monitoring module was still actively used. So, many of you justifiably asked for an automated way to migrate everything, easily, at once. Today, we offer you exactly that. With this release, you can now migrate dashboards, menu items, host/service actions and roles. A CLI command is responsible for that. Please read the migration documentation on how it works.
I’ve also promised an automated way of migrating wildcard filters in existing Icinga DB URLs and restrictions. This is of course also a part of this release! The upgrade documentation has been updated and shows how to use it.
- Restriction and URL migration #932
Fixes
Some of you have custom actions configured for hosts or services. Depending on the macros used, these may have caused an object’s detail view to break. This was entirely our fault and the problem is gone now. Another fault of ours, is that protected custom variables were visible to users who weren’t allowed to see them. Now they don’t, as expected. A less problematic, but still undesirable, issue was that if you sort a host’s services by severity, the order of them was somewhat unpredictable. The order should be fine now.
- Action macros break object details #900
- Protected custom vars not obfuscated #911
- Sorting by Severity on a Host results in random order #915
Icinga Web
You can find all issues related to this release on our Roadmap.
PHP 8.3 Support
This time we’re a little ahead for once. PHP 8.3 is due in a week, and we are compatible with it now! There’s not much else to say about it, so let’s continue with the fixes.
- Support for PHP 8.3 #5136
Fixes
You may have noticed a dashboard endlessly loading in the morning after you got to work again. The web server may also have stopped that with a complaint about a too long URL. This is now fixed and the dashboard should appear as usual. Then there was an issue with our support for PostgreSQL. We learned it the hard way to avoid such already in the past again and again. Though, this one slipped through our thorough testing and prevented some from successfully migrating the database schema. It’s fixed now. Another fixed issue, is that the UI looks somewhat skewed if you have CSP enabled and logged out and in again.
