Comentários (6)

1 thomas.quadflieg comentou às Link permanente

Great! The new View looks much better. If you just see the domain state and an aggregated value like "n resources are not working", the overview is not really usefull. So, I'd like to see the top-level resources. I'd also like to trigger actions and (this is more important) be able to go into detail from this point, e.g. select a Top-level ResourceGroup and switch to a view that shows all members with their states.
Is it possible to decrease the height of the rows, e.g. by cutting the state? We have more than 7 top-level-resources, so you wouldn't see them in 1 page

2 nukite8d comentou às Link permanente

I like the new overview more than the old one, too.

But I would prefer to prevent actions, because the compound state could confuse and result in wrong behavior.
E.g.: "eMail Hosting0" has the green state OK, but you can't request Offline, because the OpState is already Offline. Furthermore there has to be a request on the top-level-group (or Nominal=Offline), which isn't shown. So the Operator won't look for Requests and its comments for a reason.
Therefore I would like to just allow a drill-down in a domain specific dashboard/view.

3 nukite8d comentou às Link permanente

Last but not least,
I not sure how feasible the graphical view of all connected domains is, when we connect our >100 Domains.


4 BerndJostmeyer comentou às Link permanente

The 100 domains you only see in the upper left - in the domain tree. Everything else is always only in the context of one domain - what is the typical number of top level resources you have for domains? Is it more than 10?

5 Rüdiger Dahlke comentou às Link permanente

Hello Josi,
our greatest (and perhaps most important) clusters contain 17 top-level-rg's. But back to the new dashbord: the volume bars are much better then the the gauges. To my mind triggering Actions should be possible on every place on every dashboard. But I'm missing the icon (Männchen) representing a request, see resource "eMail Hosting0": status = offline and color=green. It should be clearly visible that here is an active request.

6 WolfgangSchäberle comentou às Link permanente

Hi. Thanks for your feedback and this interesting discussion.
Let me try to answer some of your questions and add my own thoughts:

Because this is an overview dashboard, the idea was to present the top-level resources in a high-level way without all the details. This is why we used the simple List widget. This List widget focuses on the compound state of resources and the only additional information that is provided is the observed state. You can use this List widget to easily filter by compound state and initially you will always see the worst status at the top (resources are grouped by compound state).
If we add more information for each resource, we very soon end up with additional columns for desired state, operator request yes/no, suspended yes/no, ...
Then we would have to use a table widget and it gets a a lot more complicated to grasp the most important information quickly (which - on an overview dashboard - should be the compound state of top level resources).
This is why - in my opinion - we should keep this list of resources which is presented on the overview dashboard very simple.
And, after following this discussion, I also think that we should NOT offer resource actions on this level. The only actions that should be shown are to open the Properties of a resource and to drill-down into the domain to a new page that shows ALL information (requests, states, children, relations). From there you can issue all the requests.
What do you think about this reasoning?
By the way: Regarding the number of top level resources displayed in the list. If there are more resources than can be displayed, the list of course receives a scroll bar to scroll down to the lower resources. In addition, you will initially see the resources with the worst compound state at the top - so you should always see the resources that you need to focus on when resolving problems. Furthermore you can also use the Filter text box to filter resources by name.

Incluir um Comentário Incluir um Comentário