Re: [wildfly-dev] Domain Overview design

+100 on Jason's comment thanking you for posting this. On 7/24/14, 12:05 PM, Jason Greene wrote: That seemed intuitive to me. I don't get though why some boxes are different sizes from others on "Second Iteration: Stacked heatmap". On "First draft heatmap – Server Group view for 'availability'" I could somewhat get that, as different server groups can vary in size based on # of servers. My instinct is something like alphabetical is better. The color already lets me easily find and identify things where availability/status is relevant to what I want to do. But when it's not relevant to what I want (say I want to work with server-X for reasons completely unrelated to availability) then I need to rely on location to find what I want quickly. Note that multiple servers in a domain can have the same name; it's the host (as in Host Controller) + server name combination that must be unique. If the colors are green and grey, maybe not. But in a number of examples you use green<->red, with grey too, and I think that's pretty intuitive. Red = bad, green = good, yellowish = in between, grey = the good/bad aspect is out-of-scope. I think we need a better understanding of what alerts are. In general, I like the idea of the occurrence of some kind of negative event tends to shift the color away from green and toward red. But what constitutes a negative event? How much control does the user have over that definition? How much control does the user have over how much different events shift the color? Please be cautious about the Alerts notion in your design. WildFly doesn't actually have the kind of altering system that many might be thinking of when they imagine this kind of thing. So it would have to be developed. That's something we want to do, and Jeff Mesnil is doing some of the foundational work, but it's not there yet and it's a big job competing with lots of other big tasks. So, we want it, but the more a UI design depends on a complex alerting system, the riskier it is that a needed feature won't be there. Re: some of the questions, on the "Questions" page: "What are the states for server availability?" On "Not available" and "Failed" we have no notion of why a server was taken down; i.e. the admin takes it down, but whether they did so due to issues or for some other reason, we have no idea. We can distinguish a crash from an administrative shutdown. Also, there are other aspect of a server's running state that complicate things. We are adding the ability to put a server in "suspending" and "suspended" states where it moves to not accepting normal end user requests but is still running. This isn't an "error" state; the admin has chosen to put the server in that state. There's also a similar notion regarding how consistent the server's running state is with its persistent configuration. Admins can make configuration changes that will not take effect until the server is reloaded or restarted. I'm not sure if those things are well represented on a green-yellow-red color continuum because they are somewhat different from server health. But they are important pieces of data to visualize. "How does the Alerts tab fit in with the *current* Notification message queue?" Heiko Braun knows better, but I don't see a close fit. The current queue isn't really based on any sort of server-push of events. The console makes administrative requests and gets responses; if relevant that request/response results in stuff in the queue. But anything that happens outside of those requests/responses is unknown to the console. Cheers, -- Brian Stansberry Senior Principal Software Engineer JBoss by Red Hat