Today we’re announcing the availability of Icinga Dependency Views v1.0.1. Updated packages are available.
In This Release
Sometimes it feels like pure irony: you set up beautiful, custom views in Icinga; only to find they don’t show what you expect. Or worse, they proudly display the wrong information.
This delightful surprise could happen when Icinga DB Web restrictions were applied to users exploring our Dependency Views.
The goal, of course, is to help you trace problems with handy breadcrumbs from the current object all the way up to the root cause. But those breadcrumbs occasionally had a mind of their own: sometimes missing, sometimes duplicated, and sometimes leading you astray.
As if that wasn’t enough excitement, the dependency map could get itself so confused about whether it was up to date that it fell into an endless reload loop. And if it didn’t do that, it might simply skip parts of larger hierarchies, hiding things that really should have been shown.
Structural information was supposed to remain visible even if you didn’t have permission for object details, but thanks to this bug, it ended up more hidden than intended.
We’ve untangled these loops, cleaned up the breadcrumbs, and your Dependency Views should now behave the way you’d reasonably expect – or at least no longer in quite such an chaotic fashion.
