Skip to content
This repository has been archived by the owner on Sep 22, 2024. It is now read-only.

Update traffic data format #24

Closed
baransu opened this issue Apr 1, 2017 · 8 comments
Closed

Update traffic data format #24

baransu opened this issue Apr 1, 2017 · 8 comments
Assignees
Milestone

Comments

@baransu
Copy link
Contributor

baransu commented Apr 1, 2017

Netflix/vizceral#59 got merged into Vizceral recently. It adds entryNode property and removes requirement for INTERNET node. It also allows two way message passing in our cluster view.

Things we have to change to update to version 4.4.0:

  • change focused -> focusedChild
  • for every graph add entryNode property describing graph entry node
  • replace one, one way connection to entryNode with warnings with two, one way connection without it
@arkgil
Copy link
Contributor

arkgil commented Apr 2, 2017

It is related into traffic view, right? I'll look into it as soon as I'm finished with Elixir stuff 🙂

Does this update mean that there won't be INTERNET node, and we will have bi-directional particles flow?

@baransu
Copy link
Contributor Author

baransu commented Apr 2, 2017

Correct :)

@michalslaski
Copy link
Member

Very cool.

BTW, in one of the Vizceral examples I saw force directed graph layout demo. Can we give it a try in the second level, where we render message passing?

@baransu
Copy link
Contributor Author

baransu commented Apr 2, 2017

I'll try to look into it.

@baransu
Copy link
Contributor Author

baransu commented Apr 6, 2017

@arkgil @michalslaski @mentels This change it crucial for us right now because a lot of people are trying EPL in recent days. These changes will fix no nodes in /traffic view when only one node in cluster. After getting this resolved on both front and backend we should release new version asap.

@arkgil
Copy link
Contributor

arkgil commented Apr 6, 2017

I'll try to look into it this evening 🙂

@baransu
Copy link
Contributor Author

baransu commented Apr 6, 2017

@arkgil Are going to look into it today or can I?

@arkgil
Copy link
Contributor

arkgil commented Apr 6, 2017

You can always look into issues, I'd be happy to help :) I don't have much time lately, sorry for delay.

EDIT: but I'm looking into it right now. Although extra pair of eyes does not harm anyone 😄

@baransu baransu self-assigned this Apr 6, 2017
@baransu baransu mentioned this issue Apr 6, 2017
5 tasks
@baransu baransu added this to the 0.6 milestone Apr 6, 2017
baransu added a commit that referenced this issue Apr 10, 2017
Update elm-webpack-loader and enable forceWatch
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants