search

weaveworks / scope

Monitoring, visualisation & management for Docker & Kubernetes
https://www.weave.works/oss/scope/
Apache License 2.0
5.85k stars 709 forks source link

Big topology overview (1000 nodes) #1614

Open davkal opened 8 years ago

davkal commented 8 years ago

From dockercon:

We need some way to show apparent 1000 entities on screen at once, representing all of the individual containers in your cluster — even if there's no immediate user story that's solvable in that view, just so it's clear Scope works at that scale. They needn't be the fully-realized nodes we have in the current layout. Maybe they are just immobile points without edges e.g. a grid view, and you need to interact to get more detail.

peterbourgon commented 8 years ago

IMO a good starting point here is the Scope UI Research doc, pp. 12–14.

rade commented 8 years ago

From discussion on slack...

This mode is also known as "pride mode" - "look at all my nodes!". Hence a table/list won't do, since that doesn't show all nodes at the same time.

pidster commented 8 years ago

A grid of nodes enables a higher density view than a tabular/list, which would likely lead to some scrolling at a certain number of entries.

peterbourgon commented 8 years ago

My mistake for writing tabular, in my mind I meant "like a table" i.e. the grid view.

lukemarsden commented 8 years ago

Random thought: maybe at a certain number of nodes you could zoom out to Adrian Cockroft's deathstar?

fast-delivery-devops-israel-78-638

The point isn't really to be able to individuate the nodes/services/containers, rather to get a sense of their magnitude I guess?

rade commented 8 years ago

That's called a connectogram, and is A.N.Other view. It's closer to the topology view, in that it has both nodes and edges. Hence is a better fallback than a grid view. It's probably a lot more expensive to render though.

peterbourgon commented 8 years ago

a.k.a. chord diagram

2opremio commented 8 years ago

Related #1092

rade commented 8 years ago

maybe at a certain number of nodes

We'd probably want to use a hysteresis for any automatic switching of modes, since otherwise the UI can become very unstable. And we'd probably want to take into account edge count too. Or have some more sophisticated measure.