In <AANLkTi=jrkDGhdhGaLFg5ut9QtvXKu46UfeRmpqe4ky9 at mail.gmail.com> Chris Wopat <me at falz.net> writes:
I'd love to see an option for the "non-green view" (bb2) to be grouped by the "page" attribute in bb-hosts. I would visualize this as still having a list one one page but separated by the title of each "page" while maintaining the page sort order as in the main view.
From what I can tell this functionality would live in bbgen, I looked through its help file but didn't see any option to enable this.
Correct, the bb2 page doesn't have any structure.
I would see this as a useful way to assist in troubleshoot or to organize what systems to fix during outage or possibly scheduled maintenance where you may have a large portion of your hosts down. For example, we have a page for the core of our network that's first in bb-hosts. Having this always at the top instead of mixed in with 100's of other things we would be great.
Why can't you use the new "Critical Systems" view and assign different priorities to the systems ? E.g. your core network infrastructure is priority 1, critical servers priority 2, and the rest priority 3 (or lower).
Is this feature on the roadmap?
No.
The nongreen page ("bb2" in the older versions) is a bad idea, in my opinion. Trying to fit every non-green status into one single page might work if you have a very small setup, but it just doesn't work at the datacenter level - e.g. right now I have 3575 non-green statuses split over 2650 hosts. And that's a normal Wednesday morning. I stopped generating the nongreen page a long time ago.
Even for a small setup it quickly becomes unmanageable, because an event-log entry from a Windows server will (nearly) always make the non-green page go red.
So there are no enhancements planned for the nongreen page. If anything, I would like the static HTML pages (those generated by xymoongen / bbgen) to entirely disappear and be replaced with dynamically generated pages. Then we can start discussing how to configure what they should look like, and in the end we may end up with something that you can configure to work the way you describe :-)
Regards, Henrik