BBmap question/suggestion
Posted: Sun May 26, 2013 10:28 am
Hello,
I was looking at the BBmap component and have a suggestion. Our old in-house monitoring tool presented data much the same way as BBmap, but as the number of hosts and services grew it became less useful since we could only see a portion of the results at any one time. If you consider problems to be the interesting points, it became a large sparse array. We added a filter selection to the display to allow it to show all hosts/services or only host/services with problems. So any rows or columns that were all 'green' or acknowledged/scheduled_downtime were hidden. That made it much easier to spot problems across hosts and services at a glance. (like the operations center view, but in a grid).
Our hosts are automatically sorted by service group and can optionally be filtered by service group or a string in the hostname/description.
I would really like to be able to compact the array to show problem hosts/services. This may be simple to implement, but I've been too swamped to spend any time on it myself. (took a long holiday just to get the time to post this suggestion
I was looking at the BBmap component and have a suggestion. Our old in-house monitoring tool presented data much the same way as BBmap, but as the number of hosts and services grew it became less useful since we could only see a portion of the results at any one time. If you consider problems to be the interesting points, it became a large sparse array. We added a filter selection to the display to allow it to show all hosts/services or only host/services with problems. So any rows or columns that were all 'green' or acknowledged/scheduled_downtime were hidden. That made it much easier to spot problems across hosts and services at a glance. (like the operations center view, but in a grid).
Our hosts are automatically sorted by service group and can optionally be filtered by service group or a string in the hostname/description.
I would really like to be able to compact the array to show problem hosts/services. This may be simple to implement, but I've been too swamped to spend any time on it myself. (took a long holiday just to get the time to post this suggestion