-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
Rewrite Graph visualization with Cytoscape.js #46784
Comments
Pinging @elastic/kibana-app |
Three areas we should pay attention to. Thanks, @peterschretlen
|
Important points, thanks for noting them down. About the dependencies one: cytoscape.js is basically a standalone lib, just relying on two small helpers: https://github.com/cytoscape/cytoscape.js/blob/unstable/package.json#L159 |
Pinging @elastic/kibana-data-discovery (Team:DataDiscovery) |
Pinging @elastic/kibana-visualizations @elastic/kibana-visualizations-external (Team:Visualizations) |
Closing this because it's not planned to be resolved in the foreseeable future. It will be tracked in our Icebox and will be re-opened if our priorities change. Feel free to re-open if you think it should be melted sooner. |
Currently the graph visualization in the Graph app is rendered with Angular.js and the d3-force plugin, which is limiting in two ways:
Cytoscape.js offers solutions for both of these problems because it uses canvas to render and is entirely pluggable. Other teams building network-like visualizations in Kibana also have opted to use cytoscape.js as the underlying library, which might make it possible in the future to have a unified "elastic-charts like" graph visualization that layers on top of cytoscape.js and makes experience with graphs across Kibana consistent.
The text was updated successfully, but these errors were encountered: