-
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
Flow graphs (Sankey visualization) #4716
Comments
👍 |
1 similar comment
+1 |
Same could be used to show relationships in firewall logs. Three "panes" Left, incoming connections I think the big problem to solve is how to create a generic visualization that can be used with different types of data. But, Packetbeat used to have a panel sort of like that for Kibana 3 |
+1 |
via @JalehD
|
https://github.com/james-irwin/enronsankey/ has some sample code we could use? |
+1 |
1 similar comment
+1 |
++ |
+1 |
4 similar comments
+1 |
+1 |
+1 |
+1 |
There are any deadline for this issue? |
Coming from Splunk where they have this available, I'll add that the Vega implementation seems WAY more convoluted than doing this over there, which boils down to using a simple query like this and passing it to the sankey visualization type:
ref: https://docs.splunk.com/Documentation/SankeyDiagram/1.6.0/SankeyDiagramViz/SankeySearchDataFormat |
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. |
+1 |
I would like to use ELK to analyze user navigation patterns (ala Apache Access logs) and wondering if a User Flow graph similar to Google Analytics could be added as a visualization.
I have not quite figured out the document structure that could power that yet but I imagine that each document would be a session and it could maybe have 6 fields for the 1st visited page, 2nd visited page and so on...
Here's a sample User Flow graph from google analytics:
The text was updated successfully, but these errors were encountered: