Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

"At-A-Glance" Type Views #16

Open
jnovack opened this issue Aug 30, 2022 · 0 comments
Open

"At-A-Glance" Type Views #16

jnovack opened this issue Aug 30, 2022 · 0 comments
Labels
Enhancement New feature or request

Comments

@jnovack
Copy link

jnovack commented Aug 30, 2022

The default container view of all stopped/running containers does not give the viewer any sense of context. Are all services healthy? Are all services up (i.e. 1/1, 3/3, or 9/9)? Is the environment good?

In the container world, I don't care about containers. Kittens vs Cattle. I want to know the environment is healthy, if the stacks are running, if the services are fully scheduled. That's "green" to me.

If I care about a container or diving deep, then let me drill down, but I feel my first layer view should tell me all the things I need to know. Seeing a list of containers, both stopped and running is confusing to know if "my environment is healthy or not". A list of containers is only useful when I have less than 5 containers and I know and care for all of them (kittens). In a "cattle" environment, I care about stacks, services, and health checks. I can't remember the names of all 36 of my running containers.

The stack details view has all the information I need to know I'm good.

image

All of my services are fully scheduled (1/1 and 3/3), and the last update was what I expected it to be. I don't need to look at any container because I know everything is up.

@rrroyal rrroyal added the Enhancement New feature or request label Oct 27, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants