Import, export and clone saved objects

[TiNico22]

As visualize configuration can be more complex in Kibana 4 than in 3 and visualize are part of dashboard, import / export feature should be great to share visualize with other people.

Update: request applies to dashboard as well, see #1551

[spalger]

Are you trying to share with someone who has access to your elasticsearch cluster? If so, that's as easy as sending your url.

There's also this little button:

[spalger]

That said, I personally don't think sharing a visualization from one cluster to another would be too useful, since the other person will have different data, indices, fields, etc.

It might be useful for tutorials, or blog posts, but even then the author could provide just the hash part of the url.

Thoughts?

[otisg]

Cross-cluster sharing may not work, but sharing the URL with people who have access to the same cluster/index is handy!

[TiNico22]

I was talking of the export shema feature from kibana 3

Idem for the load feature from kibana 3.
The same apply for visualize and dasboard

We are sharing dashboard shema without other people whitout having network access to each other ELK servers. This helps, as blog post & tutorial samples, to start a new deployement with some sample from friends without having to rewrite everything.

[robozu]

As a workaround you can go to settings -> objects -> visualizations and copy all the fields from there and paste them into another search (create a new one and save it) even on another elk server

[TiNico22]

@robozu thanks for the advice
Not as easy as the export schema from K3. It works also for dashboard.
But with K3, exporting a dashboard was the equivalent of exporting a dashboard + all related visualize in K4
The major issue is, if I have a lot of visualize, to export once by once. I would rather have an "export all my visualize" feature.

[nabheet]

Also, if I have mutiple environments like Dev, Test and Production with separate ELK infrastructure, this feature would be nice so we can migrate visualizations from environments. Unless there is another way to accomplish the same task.

[abh1nav]

+1 for the dashboard export feature - really handy for being able to move between dev, test and prod

[leonardpunt]

+1, for the same reason as mentioned by @abh1nav

[calaldees]

+1

[t3chn0m4g3]

+1

[spalger]

related issues: #2100 and #2695

[agirbal]

Copying comment from related ticket:
URLs are great way to share but can get messy.
Some users are used to manipulating dashboard through JSON, which makes it easy to modify parameters cleanly. Some info here:
http://blog.trifork.com/2014/05/20/advanced-kibana-dashboard/
Additionally can be useful to share searches and visualizations.
thanks!

[shayts7]

+1

[niemyjski]

We really need the ability to import and export dashboards to a gist. We have an open source project that uses es and it's really nice for us to send our customers hosting locally a nice looking dashboard..

[matthewgaulin]

+1 to help with dev/test/prod synchronization

[wadewilliams]

👍 @spenceralger: re:

"I personally don't think sharing a visualization from one cluster to another would be too useful, since the other person will have different data, indices, fields, etc."

For our use case, we have several elasticsearch instances that share the same indices and fields, but different data. So while the the data changes, the format won't. This would be super helpful.

Thanks all

[w33ble]

👍

[wadewilliams]

FYI: We were able to work around this by using Elasticdump -- simply pull the .kibana mapping and data from one instance and shove it into another :)

[JohnGarbutt]

So I really liked the kibana 3 ability where you have a set of "static" dashboards stored in json files on disk, and managed via config management, rather than everyone being able to change everything inside the elasticsearch index.

[BeniGal]

+1

[ch40s]

+1000 :)

[davidbono]

👍

[mserdur]

+1

[Inderjeet26]

+1

[ferranmunoz]

+1 for dev/test/prod synchronization
For now I am using elasticdump.

[milanchandna]

+1 very helpful to share the basic dashboard/visualizations. sharing to get new users quickly get started. And not sharing the url to avoid conflicts from modifications. each user should have their own copy instead of sharing one.

[ghost]

+1 Read it being available from 4.1.0 release

[hex0cter]

+1

[nocturnal3d]

+1 we have multiple deployed environments before we productionise the dashboards.

[Guinoutortue]

For the moment I use the following script with a crontab every night! You have to create a folder /home/kibana-backups/

#!/bin/sh
#save_kibana_task.sh
#take a parameter for naming the backup

/usr/bin/curl -XPOST localhost:9200/.kibana/_close
/usr/bin/rm -R /home/kibana-backups/.kibana-$(date +\%d\ )
/usr/bin/cp -R /var/lib/elasticsearch/<your_CLUSTER_name>/nodes/0/indices/.kibana /home/kibana-backups/.kibana-$(date +\%d\ )
/usr/bin/curl -XPOST localhost:9200/.kibana/_open

sh save_kibana_task.sh <suffix_name_for_backup>
And you can restore with this :

#!/bin/sh
# restore_kibana_task.sh

elasticcluster=<your_CLUSTER_name>

/usr/bin/curl -XPOST localhost:9200/.kibana/_close
/usr/bin/rm -R /var/lib/elasticsearch/${elasticcluster}/nodes/0/indices/.kibana/*
/usr/bin/cp -R /home/kibana-backups/.kibana-$1/* /var/lib/elasticsearch/${elasticcluster}/nodes/0/indices/.kibana/
/usr/bin/chown -R elasticsearch:elasticsearch /var/lib/elasticsearch/${elasticcluster}/nodes/0/indices/.kibana
/usr/bin/curl -XPOST localhost:9200/.kibana/_open

sh restore_kibana_task.sh <suffix_name_for_backup_to_restore>

Of course give them necessary right for bash script +x!!!
You can copy a folder to an other server and restore. Sometimes you will need to restart elasticsearch after a restore.
(For Linux / sorry Windows users :-( )

[jim-davis]

I wrote a Ruby script that can copy a dashboard, its visualizations, and their saved searches from one Kibaba 4 cluster to another.
https://github.com/jim-davis/kibana-helper-scripts

[ajay2881]

Hi Jim, How to use the script?

[jim-davis]

It's a ruby script intended to be run from the command line on Linux.
To use it you must first install the Ruby language on your workstation.
If you have ruby, you can run the script by executing

ruby copy-kibana-dashboard.rb --help

You will need to know the host and port of the source and destination ES clusters
and the ID of the dashboard

example

ruby copy-kibana-dashboard.rb --from-host old-cluster-host --to-host
new-cluser-host --dashboard myDashboard

On Wed 24/06/15 10:16 AM , ajay2881 notifications@github.com sent:

Hi Jim, How to use the script?

—
Reply to this email directly or view it on GitHub [1].

Links:

[1]
#1552 (comment)

[ajay2881]

Thanks Jim

[WCMinor]

+1 built in export/import

[carlosvega]

+1

[ddes]

+1

[EliasGoldberg]

+1

[wasmum]

+1

[wasmum]

The issue is not dumping and restoring, but importing a dashboard you had on 3 to 4 or from machine to machine without having to mess alter the index.

+1

[lukasolson]

We won't be supporting export/import from Kibana 3 to Kibana 4. However, you can currently import/export from one machine to another. See #3573.

[ShayanZafar]

+1