Add Sankey visualizations to Dashboards

[Jon-AtAWS]

Is your feature request related to a problem? Please describe.

It's not particularly a problem... I was trying to play around with the Vega code here: https://github.com/danielneil/ELK-Sankey with little success. Is this something that we can onboard as a visualization?

Describe the solution you'd like

Add a "Sankey" visualization as a primary visualization type.

Describe alternatives you've considered

Vega. Yuck.

Additional context

From the above link:

[joshuarrrr]

@Jon-AtAWS To help us prioritize various new visualization types, can you provide a little more context of your Sankey use-case? The type of data you're looking to compare, and the types of insights you're looking for.

[ahopp]

@Jon-AtAWS revisiting @joshuarrrr question: Can you add some context on some of the use case you'd like to use this for?

I've only used this visualization type to map one or more paths through a set of stages but the graphic above seems to be mapping proportionally from side A and side B (i.e., more like an alluvial diagram) e.g., the above graph doesn't have any node intermediate nodes. I'd assume you'd like this capability as well? My assumption is you would want to be able to create both both and alluvial diagram (see Example A below) and a Sankey diagram (Example B)

Example A: A user has two categories, John and Andrew, that connect to three other categories, Zoo, Mall, and Aquarium. Some of those connections are heavier than others. For instance, Andrew has a thin connection to Zoo and a much thicker connection to Mall.

Example B: A user has three categories, John, Andrew, Eli, and Josh, that connect to four other categories, Zoo, Mall, Theater, and Aquarium. These categories in turn connect to five other categories, Entrance Fees, Donation, Merch, Food, and Other, which connect to three other categories, Non-Profit, For-Profit, and Both.

EDIT: If you have a few example use cases that would be a great place to start!

[Jon-AtAWS]

Thanks for digging that out - that's exactly what I meant, a multi-stage graph. The A->B is just the degenerate version of that.