Define the requirements for the new home page

[joaquimrocha]

The current Nebraska's home page and application pages could better display the overall status of updates (which is hopefully that users are looking for).
So we need to understand what information to display in those views, essentially how to provide a global view of the updates: how many instances are updating? how many have reported errors? what's the breakdown of instances for groups/version...

This is easier to convey in the single application view, however, we can argue that all apps defined in a Nebraska deployment may be related. Therefore, besides refining how to display all apps, we could also show at least a count of the clients served, regardless of their applications, and for each instance view, maybe also show information for different applications if they happen to have more than one.

[illume]

Probably as we ask users about what jobs they want to do with the home page we will learn what's important to who.

Things that come to mind...

Related to progress

• users wanting "update progress" makes me think they might want regular updates
• do they need to report update progress to someone? If so, this might imply some sort of data export.
• do they need an alert when some level of updates complete/fail? Are they sitting around waiting for 80%/100% to be updated?
• why do they want to know about update progress?

Global view

Are there even users of separate applications that are only interested in a single one? Seems this is deployment centric, and then may benefit from an option.

[illume]

For "number of active clients", and "number of instances" seeing a number like 142 doesn't tell you how many there usually are or how many there were ten minutes ago. There could be 10,000 instances usually or 142 instances usually... who knows?

When looking at alerts it's often nice to drill into a time period. Last 24 hours is good here! Perhaps also a range would be nice.

Is it also useful to show the status(nr. active clients, nr. instances) for a given time range?

[illume]

I like that the application view is the home page when there's only one application. Having views responsive to the configuration like this will make it a lot more usable.

[joaquimrocha]

For "number of active clients", and "number of instances" seeing a number like 142 doesn't tell you how many there usually are or how many there were ten minutes ago. There could be 10,000 instances usually or 142 instances usually... who knows?

When looking at alerts it's often nice to drill into a time period. Last 24 hours is good here! Perhaps also a range would be nice.

Is it also useful to show the status(nr. active clients, nr. instances) for a given time range?

We have a predefined set of options for the time range. It's not very flexible at the moment, so maybe you mean we should show a couple of options + a start/end chooser?