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

Scope graph doesn't re-org itself to show structure of containers and flow of connections #1935

Closed
mjlodge opened this issue Oct 18, 2016 · 3 comments
Labels
chore Related to fix/refinement/improvement of end user or new/existing developer functionality component/ui Predominantly a front-end issue; most/all of the work can be completed by a f/e developer
Milestone

Comments

@mjlodge
Copy link

mjlodge commented Oct 18, 2016

Running Sock Shop demo app, Scope's container view does not change as network traffic begins to flow, resulting in edges drawn across nodes, with little information about the structure of the application.

Hitting refresh will cause the graph to be re-drawn with structure. Otherwise the layout does not change.

To reproduce on Docker Mac: start Docker, follow instructions to clone sockshop github repo, cd to docker-only directory. Edit last line of compose yaml file to be "-r 100000". Do docker-compose up -d

Wait about 30s for the traffic generator container to start. Observe that a few containers show connections between them, but the layout does not change.

Do docker-compose scale user-sim=6. Note that you will have to hit the refresh icon several times to get the graph to change.

cc @pidster

@mjlodge mjlodge added the bug Broken end user or developer functionality; not working as the developers intended it label Oct 18, 2016
@mjlodge
Copy link
Author

mjlodge commented Oct 18, 2016

The graph is also drawn "upside down" in this screen shot -- not showing top-to-bottom left-to-right flow:
screenshot 2016-10-17 13 23 57

@2opremio 2opremio added this to the 0.18/1.0 milestone Oct 18, 2016
@2opremio
Copy link
Contributor

2opremio commented Oct 18, 2016

@mjlodge This is a tricky one, since it's hard to find the right balance to avoid dancing nodes.

@mjlodge
Copy link
Author

mjlodge commented Oct 18, 2016

I can see that. But the layout yesterday was moribund in the extreme. It hardly ever changed. I think the current setting is way to soporific :-)

@2opremio 2opremio added the component/ui Predominantly a front-end issue; most/all of the work can be completed by a f/e developer label Oct 21, 2016
@2opremio 2opremio modified the milestones: October2016, kubecon, re:Invent, November2016 Nov 3, 2016
@davkal davkal modified the milestones: December2016, EOY 2016 Dec 13, 2016
@rade rade modified the milestones: EOY 2016, Next, Backlog Jan 11, 2017
@rade rade added chore Related to fix/refinement/improvement of end user or new/existing developer functionality and removed bug Broken end user or developer functionality; not working as the developers intended it labels Jul 14, 2017
@mjlodge mjlodge closed this as completed Apr 23, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
chore Related to fix/refinement/improvement of end user or new/existing developer functionality component/ui Predominantly a front-end issue; most/all of the work can be completed by a f/e developer
Projects
None yet
Development

No branches or pull requests

5 participants