# How industrialize a Kibana solution?

**URL:** <https://discuss.elastic.co/t/how-industrialize-a-kibana-solution/24802>\
**Category:** Kibana\
**Created:** [July 2, 2015, 12:43pm UTC](https://discuss.elastic.co/t/how-industrialize-a-kibana-solution/24802 "2015-07-02T12:43:30Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![cherah30](https://avatars.discourse-cdn.com/v4/letter/c/b487fb/32.png) [@cherah30](https://discuss.elastic.co/u/cherah30)\
**Post date:** [July 2, 2015, 12:43pm UTC](https://discuss.elastic.co/t/how-industrialize-a-kibana-solution/24802/1 "2015-07-02T12:43:30Z")

</div>

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 (4 and higher) solution, is there a solution to reuse dashboards (with export or with a other way)? if Other way, I would like to indicate me?

---

<div class="post-metadata">

**Author:** ![tbragin](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tbragin/32/45166_2.png) [@tbragin](https://discuss.elastic.co/u/tbragin)\
**Post date:** [July 2, 2015, 9:50pm UTC](https://discuss.elastic.co/t/how-industrialize-a-kibana-solution/24802/2 "2015-07-02T21:50:00Z")

</div>

Everything you see in the dashboard in encoded in the URL, so you can modify parts of the URL to vary parameters you need for your users (see [related thread](https://discuss.elastic.co/t/what-happened-to-templated-scripted-dashboards-in-kibana-4/65)).

---

<div class="post-metadata">

**Author:** ![Joe\_Fleming](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/joe_fleming/32/3561_2.png) [@Joe\_Fleming](https://discuss.elastic.co/u/Joe_Fleming)\
**Post date:** [July 3, 2015, 12:24am UTC](https://discuss.elastic.co/t/how-industrialize-a-kibana-solution/24802/3 "2015-07-03T00:24:34Z")

</div>

One solution would be to do something with the exporting feature that was added in Kibana 4.1. It leaves you with JSON data, so you could start from a "base" dashboard, export that, and use some custom built application to modify it as needed.

---

<div class="post-metadata">

**Author:** ![cherah30](https://avatars.discourse-cdn.com/v4/letter/c/b487fb/32.png) [@cherah30](https://discuss.elastic.co/u/cherah30)\
**Post date:** [July 6, 2015, 12:22pm UTC](https://discuss.elastic.co/t/how-industrialize-a-kibana-solution/24802/5 "2015-07-06T12:22:16Z")

</div>

Than...nks. You make me save valuable time.  
However, for an export tool is complete, I think it would be interesting to add an export functionality to select both a Dashboard and some widgets (not all). Version 4.1 does not allow it.

Again thank you

---

<div class="post-metadata">

**Author:** ![cherah30](https://avatars.discourse-cdn.com/v4/letter/c/b487fb/32.png) [@cherah30](https://discuss.elastic.co/u/cherah30)\
**Post date:** [July 6, 2015, 12:25pm UTC](https://discuss.elastic.co/t/how-industrialize-a-kibana-solution/24802/6 "2015-07-06T12:25:26Z")

</div>

Thanks. Your help on the link below helped me:

> [@How to save dashboard as json file](https://discuss.elastic.co/t/how-to-save-dashboard-as-json-file/24561/2):
>
> I am using Kibana 4.1

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [July 6, 2017, 2:17pm UTC](https://discuss.elastic.co/t/how-industrialize-a-kibana-solution/24802/7 "2017-07-06T14:17:01Z")

</div>


