Hi,

Before one wonder if having a view on more than hundred objects really is something useful, I got one example just right now: some operations are taking place on our AIX infrastructure, I (as some of my users) would need having a view on all that.

Yes I know that using a custom view or else could be a solution but I insist on the un-understandable aspect of such a limitation on the Resource Status page.

Have a nice weekend.

Hi folks,

I’m adding three servers, which are not fully set up, so I got to put a downtime on them. With the hundred limit and the 114 ressources those three servers represent, I have two options:

 1. Do it on the first page, then on the second page (in fact, not really, continue to read to know why! ^^)

 2. Add type:host in addition to the single keyword I use to filter resources (which is actually a part of their name).

And probably some other twisted ways I can’t think of.

1. will result in two individual downtimes, with the risk of not setting the same parameters, and the need to copy the comment to set the same one for the second downtime, it is awfully  unergonomic and technically dirty (’cause although the exact same inputs are typed, it still is two distinct downtimes). About 2. Well… And I still can’t display all the ressources on one page then.

I’m testing live as I’m writing this post: it is even more insane… I thought I could probably use the selection on multiple pages. So I did test. I tested setting a second short downtime. Do you know what I discover? I realise that checking the “check all” checkbox (and then ask for a downtime) not only checks all the displayed resources, but the entirety of them! So, as you can see below, I actually can set a unique downtime on my 114 resources, but if I had to set a downtime only on the resources of page one I’d to select them one by one… (in other words, I thought I set up two downtimes but four have been set up actually)
 

I don’t have much time to be more precise but fact is this “new” page is a (f***** bad) joke on many levels. It looks modern compared to the old pages but functionally it is a marvellous demonstration of what not to do when designing an user interface. It has clever functionalities though, but as soon as I look closer to them I find broken/unfinished things.

Why is this limit to hundred resources displayed per page?

How displaying wrong information (in the “View by host”) is not even considered as a bug?

Moreover, if asserting that displaying more than 100 resources isn’t useful (which is utterly false), where then would be the utility to chose between the display of 20 or 30 or 40 or 50 resources?

« Le mieux est l’ennemi du bien. »

Respectueusement.

Stéphane THOMAS