Enhancement: Flow Generator & Flow viewer - linking dashboards & passing filters

[jitendra-kumawat]

Describe the feature:
Flow Generator & Flow viewer - linking dashboards & passing filters

Create a flow(inter-linked dashboard ) using Kibana dashboards and indices available in ES .
While creating flow following features are required:-

1. Choose start index and lands to default dashboard with default table view
2. Option available in dashboard to link to move to one or more dashboards
3. Edit dashboard - user can customise default dashboard to have more component ( like kibana dashboard only)
4. Dashboard and index-pattern are created programatically in this plugin so that the user don’t need to go to Kibana Dashboard Tab (for creating dashboard )and Management Tab(for create index-pattern)
5. User can Save the Dashboard flows. This is saved in ES index only so we need create new index for saving flows.
6. User can save multiple flows like this.

Flow Viewer:

1. Flow created via flow generated can be viewed in read only mode in Flow viewer module.
2. User can only browse the given set of dashboards & able to do selections to pass those as filters for next screen. In this way he is drilling the information from one dashboard to another with required filters.

Currently kibana support visualise data in single standalone dashboard for any index available in elastic search and that index must be created in kibana’s management tab before hand via create index-pattern functionality. Currently It’s not providing multiple dashboard linking in a specific flow (linear type or tree type), also passing selection(filters) on to linked dashboards. Also need breadcrumb support in flow of dashboards to support move back to specific previous dashboard.

This feature in kibana can be developed as plugin or in-code of kibana. (We prefer plugin way - tried in our poc).

Prerequisite requirement for plugin

1. indices should be available in elastic search
2. New configuration file in KIBANA which have mapping of “dashboard-link-functions” and “index name” available in ES

Follow below steps to create flow in plugin

1. Choose initial index of ES to start flow and lands to default dashboard with default table visualisation and can be edited to custom visualisations for same index using kibana edit dashboard feature.
2. Choose dashboard-link-function ( populated from new configuration file in kibaan) to create next dashboard same as links to styles and js #1
3. Follow step Change of links to styles and js #2 to create flow
4. We will save button in flow template to save the flow
5. User can go to Flow-Viewer module to browse through available list of flows

Eventual goal is to achieve two features here:

1. Developers can do the generation part via flow generator.
2. End users can only have access to Flow viewers, this can be done with roles control if needed.

For details follow the screenshots or pdf below:

⇨ ⇨ ⇨ ⇨ ⇨

Flow Generator Kibana Detailed Screen Pdf

In case needed we can have conference call or chat to discuss about our idea. We can even present our plugin POC to show case the real capability. There might be some specific implementation which we can remove on your comments so generically used by industry.

Feature raised by @jitendra-kumawat (Jitendra.Kumawat@guavus.com)/@jollyparamjit (jolly.paramjit@guavus.com)

[jollyparamjit]

We are planning this feature as generic as possible so everyone in community can give their comments so we can design better for community.

[jollyparamjit]

Hi Guys, @cjcenizal @marius-dr @tsullivan @LeeDr @bhavyarm @w33ble @weltenwort

We are expecting someone will comment on this feature, Currently we are developing for in-house usage. We were thinking incase -anything on same lines exists or planned, We can be part of that.
Quick feedback or reply will be appreciated.

Regards
Jolly / Jitendra from Guavus Inc

[cjcenizal]

@elastic/kibana-sharing @elastic/kibana-design Hey teams, could you take a look at this issue and comment?

[jollyparamjit]

Thanks!! Appreciate ur quick attention

[stacey-gammon]

Can you expand a bit on the problems you are trying to solve with this feature @jollyparamjit? I'm having a bit of a tough time following it, but from what I can tell there are a few features we are working on that may help ease some of the pain you are trying to address.

One issue is drill down links: #12560. I think this covers the issue with applying filters incrementally and opening up different dashboards, but please correct me if I am misunderstanding.

Another issue is dashboard level index patterns: #16917. It seems like this might be in line with your desire to choose the index pattern first in the flow, and then create a dashboard where all visualizations are based off that index pattern.

Another issue is dashboard templates/nested dashboards: #16919. You mention dashboard-link-function and flow template. I'm not sure I follow exactly what the dashboard link function does, but maybe it's a similar concept?

What isn't being worked on or planned for is the ability to choose an index pattern without first going into management, though we could always add that in later. Time series visual builder does something like this - letting the user choose index patterns that may not be first created in management.

Hope this helps.

[Jal619]

Hi @jitendra-kumawat/@jollyparamjit

I am explaining exact requirement with example .
Let's say we have 2 dashboards
Dashboard 1. Operating System
Dashboard 2. Browsers

In Dashboard 1 we have pie chart showing multiple Operating System like Windows,linux,Android .
In Dashboard 2 we have pie chart showing multiple Browsers like Chrome ,IE , FF etc.

When I click on Windows in Dashboard 1 then it should redirect to Dashboard 2 and should show Browsers having Operating System as Windows .

Is it possible through this?
Please suggest.

Thanks & Regards,
Jalpesh

[timroes]

Thanks a lot for all the interaction and the detailed sharing of mocks here. As @stacey-gammon pointed out in a previous comment a lot of the underlying features are already tracked in several different issues (all linked above). I would close this issue, not because we are not looking into how to bring something like that into Kibana, but in favor of the more specific issues above, so we can chunk it into manageable efforts.

Please feel free to stay with us and keep interacting on the above issues. Your feedback is highly welcome there.