# Displaying exported Kibana dashboards with JavaScript?

**URL:** <https://discuss.elastic.co/t/displaying-exported-kibana-dashboards-with-javascript/220730>\
**Category:** Kibana\
**Created:** [February 24, 2020, 10:09pm UTC](https://discuss.elastic.co/t/displaying-exported-kibana-dashboards-with-javascript/220730 "2020-02-24T22:09:55Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![EricJohnson](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ericjohnson/32/53592_2.png) [@EricJohnson](https://discuss.elastic.co/u/EricJohnson)\
**Post date:** [February 24, 2020, 10:09pm UTC](https://discuss.elastic.co/t/displaying-exported-kibana-dashboards-with-javascript/220730/1 "2020-02-24T22:09:56Z")

</div>

Hi

We are using the Enterprise Elasticsearch and Kibana to do a variety of tasks behind firewalls in client production environments. Primarily we are doing various monitoring tasks and running machine learning models I built to do forecasting. We have a public-access endpoint system (Node.js) that is used to display data to employees and clients.

I need to export the Kibana dashboards I've built and somehow display them on the internet side of the firewalls. Is there a JavaScript framework or library that can do this? I can get \*.ndjson files but how do we interpret them?

PDF's, PNG's, or iFrames will not work here because we need dynamic plots that update based on filters, etc., and the iFrame URL is not accessible from the system that needs to render the stuff.

Thank you!

---

<div class="post-metadata">

**Author:** ![tsullivan](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tsullivan/32/31077_2.png) [@tsullivan](https://discuss.elastic.co/u/tsullivan)\
**Post date:** [February 25, 2020, 12:35am UTC](https://discuss.elastic.co/t/displaying-exported-kibana-dashboards-with-javascript/220730/2 "2020-02-25T00:35:29Z")

</div>

Using an iframe is really the only way to display data that came from Kibana in another page. You said that is not an option here, but that is the method that was built to support this use case. There isn't a way to go from the exported ndjson files back to the data: they're just configuration for Kibana saved objects.

---

<div class="post-metadata">

**Author:** ![EricJohnson](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ericjohnson/32/53592_2.png) [@EricJohnson](https://discuss.elastic.co/u/EricJohnson)\
**Post date:** [February 25, 2020, 5:06pm UTC](https://discuss.elastic.co/t/displaying-exported-kibana-dashboards-with-javascript/220730/3 "2020-02-25T17:06:29Z")

</div>

Thank you for your input, Tim.

For _now_ it looks like we are going to create a separate space in a Kibana instance and watch user access carefully while we finish the development. That way we can get some results going to the right people and work on a long term solution in the meantime.

---

<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 24, 2020, 5:06pm UTC](https://discuss.elastic.co/t/displaying-exported-kibana-dashboards-with-javascript/220730/4 "2020-03-24T17:06:30Z")

</div>

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