Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Export as JS Snippet #31244

Closed
flash1293 opened this issue Feb 15, 2019 · 4 comments
Closed

Export as JS Snippet #31244

flash1293 opened this issue Feb 15, 2019 · 4 comments
Labels
enhancement New value added to drive a business result Feature:New Feature New feature not correlating to an existing feature label impact:low Addressing this issue will have a low level of impact on the quality/strength of our product. loe:x-large Extra Large Level of Effort Meta Team:Visualizations Visualization editors, elastic-charts and infrastructure

Comments

@flash1293
Copy link
Contributor

Ability to export Kibana charts as standalone JS Snippets only relying on a public CDN for embedding in articles etc.

Use case:

I am a data scientist / developer and explore some data in a local Elastic Stack. Now I want to set up a blog article and use some charts. I can of course use PDF/PNG reporting to do that, but by doing so I loose vector graphics and additional functionality like tooltips. I could also use iframe embedding, but for this I would have to set up a public Kibana instance, run it, pay for it, configure it properly, etc.

A better solution for the user would be exporting the chart as static HTML/JS Snippet, a bit like this

<div id="mountpoint"></div>
<script src="https://cdn.elastic.co/elastic-charts.1.0.0.js"></script>
<script>
// this could also be minified
elasticCharts.render(document.getElementById("mountpoint"), {
  type: "linechart"
  data: { series: [[34,5,7,88,1,12,3], [-5,7,8,8]] }
})
</script>

When migrating to elastic-charts, the visualization layer is decoupled from the rest of Kibana anyway, which should make this possible with moderate effort.

https://cdn.elastic.co/elastic-charts.1.0.0.js being just a build of elastic-charts plus a wrapper which makes it possible to be called with minimal input.

The charts could also be made(a bit) interactive with tooltips, client side hiding/showing of data etc.

TODO: Flesh out the details and create issues

@flash1293 flash1293 added the Meta label Feb 15, 2019
@flash1293
Copy link
Contributor Author

FYI @ppisljar @timroes @markov00

@ppisljar
Copy link
Member

sounds completely doable, and once we have the interpreter and pipeline in place it should really come down to saving output from the last interpreter function and providing some wrapper code that will instantiate the chart. if the plan is to only make it work with new charts it should come at very low cost.

@timroes timroes added Feature:New Feature New feature not correlating to an existing feature label Team:Visualizations Visualization editors, elastic-charts and infrastructure labels Feb 18, 2019
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-app

@lukeelmers lukeelmers added :AppArch enhancement New value added to drive a business result labels Mar 28, 2019
@ppisljar ppisljar added impact:needs-assessment Product and/or Engineering needs to evaluate the impact of the change. loe:x-large Extra Large Level of Effort labels May 4, 2021
@exalate-issue-sync exalate-issue-sync bot added impact:low Addressing this issue will have a low level of impact on the quality/strength of our product. loe:weeks and removed impact:needs-assessment Product and/or Engineering needs to evaluate the impact of the change. loe:x-large Extra Large Level of Effort labels Jun 21, 2021
@ppisljar
Copy link
Member

ppisljar commented Aug 9, 2022

Thank you for contributing to this issue, however, we are closing this issue due to inactivity as part of a backlog grooming effort. If you believe this feature/bug should still be considered, please reopen with a comment.

@ppisljar ppisljar closed this as not planned Won't fix, can't repro, duplicate, stale Aug 9, 2022
@exalate-issue-sync exalate-issue-sync bot added loe:x-large Extra Large Level of Effort and removed loe:weeks labels Aug 11, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New value added to drive a business result Feature:New Feature New feature not correlating to an existing feature label impact:low Addressing this issue will have a low level of impact on the quality/strength of our product. loe:x-large Extra Large Level of Effort Meta Team:Visualizations Visualization editors, elastic-charts and infrastructure
Projects
None yet
Development

No branches or pull requests

5 participants