# Kibana dashboard to be picked automatically

**URL:** <https://discuss.elastic.co/t/kibana-dashboard-to-be-picked-automatically/169932>\
**Category:** Kibana\
**Created:** [February 26, 2019, 2:40am UTC](https://discuss.elastic.co/t/kibana-dashboard-to-be-picked-automatically/169932 "2019-02-26T02:40:32Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![Kathir\_J](https://avatars.discourse-cdn.com/v4/letter/k/e47774/32.png) [@Kathir\_J](https://discuss.elastic.co/u/Kathir_J)\
**Post date:** [February 26, 2019, 2:40am UTC](https://discuss.elastic.co/t/kibana-dashboard-to-be-picked-automatically/169932/1 "2019-02-26T02:40:32Z")

</div>

I have exported Dashboard using Kibana UI. Now I have json in hand. I understand that I can import the same dashboard in another Kibana instance.

My question is, is there an alternate way to apply the dashboard in another Kibana instance instead of importing dashboard?

(My use case : I have few Kibana users and I don't want them to import the dashboard instead I should be able to ship the imported dashboard json along with Kibana zip so that when user starts Kibana server it should pick the dashboard automatically)

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [February 26, 2019, 2:41am UTC](https://discuss.elastic.co/t/kibana-dashboard-to-be-picked-automatically/169932/2 "2019-02-26T02:41:50Z")

</div>

The dashboards are stored in an index in Elasticsearch.  
If the new Kibana instance talks to the same cluster, then you don't need to do a thing 🙂

---

<div class="post-metadata">

**Author:** ![Kathir\_J](https://avatars.discourse-cdn.com/v4/letter/k/e47774/32.png) [@Kathir\_J](https://discuss.elastic.co/u/Kathir_J)\
**Post date:** [February 26, 2019, 2:48am UTC](https://discuss.elastic.co/t/kibana-dashboard-to-be-picked-automatically/169932/3 "2019-02-26T02:48:06Z")

</div>

> [@warkolm](#):
>
> the new Kibana ins

Thanks for quick response.  
We have different cluster environment where I need to use the Kibana dashboard.

For more clarity,

Say I have cluster environment DEV and I have couple of dashboards and I exported the dashboards.  
Now I am going to create new cluster environment PROD. Here I would like to have the same Kibana dashboards created in DEV environment without using Kibana UI.

So, Is there anyway that I could place the json(exported from DEV cluster) in Kibana zip or Elastic zip so that when PROD environment is up, Kibana comes up with the dashboard?

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [February 26, 2019, 3:00am UTC](https://discuss.elastic.co/t/kibana-dashboard-to-be-picked-automatically/169932/4 "2019-02-26T03:00:16Z")

</div>

There's no way to do that inside Elasticsearch or Kibana, no. You could do something like that with automation though, but it would be outside the Elastic Stack.

However you can take a snapshot of the index and then restore it, but it would include everything in the Kibana index.

---

<div class="post-metadata">

**Author:** ![Kathir\_J](https://avatars.discourse-cdn.com/v4/letter/k/e47774/32.png) [@Kathir\_J](https://discuss.elastic.co/u/Kathir_J)\
**Post date:** [February 26, 2019, 3:07am UTC](https://discuss.elastic.co/t/kibana-dashboard-to-be-picked-automatically/169932/5 "2019-02-26T03:07:43Z")

</div>

Alright. Got your point.

Thanks for clarifying

---

<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:** [March 26, 2019, 3:07am UTC](https://discuss.elastic.co/t/kibana-dashboard-to-be-picked-automatically/169932/6 "2019-03-26T03:07:44Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.
