Scripted dashboards without saved visualizations

[zzzuzik]

Hi guys,

I now that we can create visualization on the fly based on an URL,
@rashidkpc gave the example here #1482:

http://localhost:5601/#/visualize/create?type=histogram&indexPattern=logstash-*&_g=(time:(from:now-2d,mode:relative,to:now))&_a=(vis:(aggs:!((params:(),schema:metric,type:count),(params:(extended_bounds:(),field:'@timestamp',interval:auto,min_doc_count:1),schema:segment,type:date_histogram)),type:histogram))

however, I have no idea how to created the dashboard on the fly because it requires pre-saved visualization

could you please give a short URL example how we can generate a dashboard based on passed index, and passed non existing visualization

Thank you

[rashidkpc]

There is currently no way to script a dashboard without first injecting a saved visualization. I'll file this as a feature request.

[zzzuzik]

Thank you @rashidkpc
As a workaround, could we issue several URLs similar the the above one that will actually save visualization with curtain names?
Next, I will use these known names to generate a dashboard.

[akashcto]

Is it possible to give some examples of a scripting with existing visualization ?

[acheriat]

My usage scenario is the following: I have n customers.
I want to create one dashboard per customer.
First, i create a dashboard for my 1st customer.
Then, I want to generate a script from this dashboard to generate a dashboards for customer 2, customer 3, ...., customer N.
Finally, i will customise each one.

The idea behind is that customers have similar but not identical needs and that for an industrialization issue, I do not want to start from scratch my development of each dashboard (suppose that dashboard = 30 widgets), for my 1000 customers (n = 1000).
My question is, in a context of industrialization of kibana solution, is there a solution to reuse dashboards (with export or with a other way)? if Other way, I would like to indicate me?

[tianchao-haohan]

+1

[kmoe]

+1
I've had to fork Kibana to hack a way of doing this. It would be great to see this feature supported in Kibana > 3.

[rashidkpc]

Related to: #4489

[kcm-internet-media]

Can you describe your approach, @kmoe ? Like @cheriatahmed , I want to make Dashboards "deployable" to users, and deploy a bunch of available dashboards to new instantiations of virtual machines hosting Kibana, mostly as per moving code from dev to prod.

Type of advice I thought I was looking for: "Export a Dashboard to a json file. Copy that file to /etc/kibana/dashboards.d/the-dashboard-you-exported.json, and then restart the server or run a command. You just gotta know that if a user chooses an available dashboard but lacks access to indices contained with visualizations, Kibana will say so."

What is "scripting" the process? Any write-up, no matter how ugly, would be good.

Alternatively, has anybody taken the approach of providing documentation to new users of Kibana in their organizations about internal websites where they can download dashboard json files for manual import? Or look at a bunch of them in exported iframes and "choose" them?

[sirhc-k]

+1

[stacey-gammon]

I'm pretty sure we have the requests from this issue covered in:

Nested dashboards - #16919
Changing an index on a visualization - #3668
and an improved export to include visualizations with the exported dashboard - #16831

Going to go ahead and close this out. Feel free to re-open with more specifics if those don't cover your requests!