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

Import, export and clone saved objects #1552

Closed
TiNico22 opened this Issue Oct 7, 2014 · 68 comments

Comments

Projects
None yet
@TiNico22

TiNico22 commented Oct 7, 2014

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

This comment has been minimized.

Show comment
Hide comment
@spalger

spalger Oct 7, 2014

Member

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:
image

Member

spalger commented Oct 7, 2014

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:
image

@spalger

This comment has been minimized.

Show comment
Hide comment
@spalger

spalger Oct 7, 2014

Member

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?

Member

spalger commented Oct 7, 2014

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

This comment has been minimized.

Show comment
Hide comment
@otisg

otisg Oct 7, 2014

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

otisg commented Oct 7, 2014

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

@TiNico22

This comment has been minimized.

Show comment
Hide comment
@TiNico22

TiNico22 Oct 7, 2014

I was talking of the export shema feature from kibana 3
sans titre
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.

TiNico22 commented Oct 7, 2014

I was talking of the export shema feature from kibana 3
sans titre
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

This comment has been minimized.

Show comment
Hide comment
@robozu

robozu Oct 29, 2014

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

robozu commented Oct 29, 2014

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

This comment has been minimized.

Show comment
Hide comment
@TiNico22

TiNico22 Oct 29, 2014

@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.

TiNico22 commented Oct 29, 2014

@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

This comment has been minimized.

Show comment
Hide comment
@nabheet

nabheet Dec 31, 2014

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.

nabheet commented Dec 31, 2014

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

This comment has been minimized.

Show comment
Hide comment
@abh1nav

abh1nav Jan 8, 2015

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

abh1nav commented Jan 8, 2015

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

@leonardpunt

This comment has been minimized.

Show comment
Hide comment
@leonardpunt

leonardpunt Jan 14, 2015

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

leonardpunt commented Jan 14, 2015

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

@calaldees

This comment has been minimized.

Show comment
Hide comment
@calaldees

calaldees commented Jan 19, 2015

+1

@t3chn0m4g3

This comment has been minimized.

Show comment
Hide comment
@t3chn0m4g3

t3chn0m4g3 commented Jan 19, 2015

+1

@spalger

This comment has been minimized.

Show comment
Hide comment
@spalger

spalger Jan 20, 2015

Member

related issues: #2100 and #2695

Member

spalger commented Jan 20, 2015

related issues: #2100 and #2695

@rashidkpc rashidkpc changed the title from Import / export visualize is missing to Import, export and clone saved objects Jan 21, 2015

@rashidkpc rashidkpc added this to the 4.1.0 milestone Jan 21, 2015

@agirbal

This comment has been minimized.

Show comment
Hide comment
@agirbal

agirbal Jan 21, 2015

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!

agirbal commented Jan 21, 2015

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

This comment has been minimized.

Show comment
Hide comment
@shayts7

shayts7 commented Jan 22, 2015

+1

@niemyjski

This comment has been minimized.

Show comment
Hide comment
@niemyjski

niemyjski Jan 23, 2015

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..

niemyjski commented Jan 23, 2015

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

This comment has been minimized.

Show comment
Hide comment
@matthewgaulin

matthewgaulin Jan 24, 2015

+1 to help with dev/test/prod synchronization

matthewgaulin commented Jan 24, 2015

+1 to help with dev/test/prod synchronization

@wadewilliams

This comment has been minimized.

Show comment
Hide comment
@wadewilliams

wadewilliams Jan 26, 2015

👍 @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

wadewilliams commented Jan 26, 2015

👍 @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

This comment has been minimized.

Show comment
Hide comment
@w33ble

w33ble Jan 26, 2015

Member

👍

Member

w33ble commented Jan 26, 2015

👍

@wadewilliams

This comment has been minimized.

Show comment
Hide comment
@wadewilliams

wadewilliams Jan 26, 2015

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 :)

wadewilliams commented Jan 26, 2015

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

This comment has been minimized.

Show comment
Hide comment
@JohnGarbutt

JohnGarbutt Feb 11, 2015

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.

JohnGarbutt commented Feb 11, 2015

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

This comment has been minimized.

Show comment
Hide comment
@BeniGal

BeniGal commented Feb 13, 2015

+1

@Malu44

This comment has been minimized.

Show comment
Hide comment
@Malu44

Malu44 commented Feb 18, 2015

+1

@rashidkpc rashidkpc removed this from the 4.1.0 milestone Mar 2, 2015

@gshively11

This comment has been minimized.

Show comment
Hide comment
@gshively11

gshively11 Mar 4, 2015

👍 for backup/restore and environment migration via export/import

gshively11 commented Mar 4, 2015

👍 for backup/restore and environment migration via export/import

@kanea

This comment has been minimized.

Show comment
Hide comment
@kanea

kanea Mar 4, 2015

+1 for the export feature - this is useful for migrations across clusters that share the same data.

kanea commented Mar 4, 2015

+1 for the export feature - this is useful for migrations across clusters that share the same data.

@gshively11

This comment has been minimized.

Show comment
Hide comment
@gshively11

gshively11 Mar 5, 2015

You may find this useful for backup/restore/deploy in kibana4. It's still experimental but is working well in our tests: https://github.com/godaddy/kibana4-backup. Feedback is appreciated!

gshively11 commented Mar 5, 2015

You may find this useful for backup/restore/deploy in kibana4. It's still experimental but is working well in our tests: https://github.com/godaddy/kibana4-backup. Feedback is appreciated!

@mkliu

This comment has been minimized.

Show comment
Hide comment
@mkliu

mkliu commented Mar 5, 2015

+1

@thorrsson

This comment has been minimized.

Show comment
Hide comment
@thorrsson

thorrsson Mar 11, 2015

Had a discussion with @rashidkpc today about exporting a Dashboard and all of it's associated objects.
Adding a comment here at his suggestion.

I think what would be nice would be a way in the UI to choose to export a dashboard's schema, and all of the related object's schemas as well for transportation between environments.
This could let you develop visualizations, dashboards and such and then promote them through to production (also track them in git or such...)
Also discussed exposing this as an API call that would return the schemas.

Along with this would need to be a way to import this dashboard definition.

thorrsson commented Mar 11, 2015

Had a discussion with @rashidkpc today about exporting a Dashboard and all of it's associated objects.
Adding a comment here at his suggestion.

I think what would be nice would be a way in the UI to choose to export a dashboard's schema, and all of the related object's schemas as well for transportation between environments.
This could let you develop visualizations, dashboards and such and then promote them through to production (also track them in git or such...)
Also discussed exposing this as an API call that would return the schemas.

Along with this would need to be a way to import this dashboard definition.

@nmors

This comment has been minimized.

Show comment
Hide comment
@nmors

nmors Mar 25, 2015

+1, feature is absolutely necessary

nmors commented Mar 25, 2015

+1, feature is absolutely necessary

@stonemaster

This comment has been minimized.

Show comment
Hide comment
@stonemaster

stonemaster commented Mar 26, 2015

+1

@rfarley3

This comment has been minimized.

Show comment
Hide comment
@rfarley3

rfarley3 Mar 26, 2015

+1

FWIW, for those who are dumping the .kibana index (without ES snapshot/restore), you only want 3 _types: dashboard, visualization, search. You may want to manually edit the dump and remove the _types: index-pattern, config. That'll make a restore successful even if you upgrade Kibana (the config is version dependent) plus it'll keep you from importing possibly invalid mapping caches (stored in the index-pattern).

rfarley3 commented Mar 26, 2015

+1

FWIW, for those who are dumping the .kibana index (without ES snapshot/restore), you only want 3 _types: dashboard, visualization, search. You may want to manually edit the dump and remove the _types: index-pattern, config. That'll make a restore successful even if you upgrade Kibana (the config is version dependent) plus it'll keep you from importing possibly invalid mapping caches (stored in the index-pattern).

@johntdyer

This comment has been minimized.

Show comment
Hide comment
@johntdyer

johntdyer Mar 30, 2015

👍 * 1000

johntdyer commented Mar 30, 2015

👍 * 1000

@aallegret

This comment has been minimized.

Show comment
Hide comment
@aallegret

aallegret commented Apr 1, 2015

+1

@ajrasch

This comment has been minimized.

Show comment
Hide comment
@ajrasch

ajrasch Apr 1, 2015

+1

On Tue, Mar 31, 2015, 9:01 PM Alan Allegret notifications@github.com
wrote:

+1


Reply to this email directly or view it on GitHub
#1552 (comment).

ajrasch commented Apr 1, 2015

+1

On Tue, Mar 31, 2015, 9:01 PM Alan Allegret notifications@github.com
wrote:

+1


Reply to this email directly or view it on GitHub
#1552 (comment).

@stegr04

This comment has been minimized.

Show comment
Hide comment
@stegr04

stegr04 Apr 3, 2015

+1 for distributed setups that parse the same type of data instead of using a shared/central setup.

stegr04 commented Apr 3, 2015

+1 for distributed setups that parse the same type of data instead of using a shared/central setup.

@t0mst0ne

This comment has been minimized.

Show comment
Hide comment
@t0mst0ne

t0mst0ne Apr 4, 2015

I had a question similar to this issue :

I need to generate 100+ search objects with line chart followed. Then pull the line chart to dashboard.
Actually, the 100+ search objects were almost the same except the "search keyword"
So what I needed to do is to manually key in the keyword one by one , then save to search , give it a name. Then from the visualization , looked from saved search, and make it a line chart , save it again.
I did for 100+ times.

What I think the more efficient way is to get one search and visualization JSON; then use script to replace the "search keyword", and then put it back.
Maybe using curl or elasticsearch.py , but is it possible to do that in kibana4 without export function ?
Thanks

t0mst0ne commented Apr 4, 2015

I had a question similar to this issue :

I need to generate 100+ search objects with line chart followed. Then pull the line chart to dashboard.
Actually, the 100+ search objects were almost the same except the "search keyword"
So what I needed to do is to manually key in the keyword one by one , then save to search , give it a name. Then from the visualization , looked from saved search, and make it a line chart , save it again.
I did for 100+ times.

What I think the more efficient way is to get one search and visualization JSON; then use script to replace the "search keyword", and then put it back.
Maybe using curl or elasticsearch.py , but is it possible to do that in kibana4 without export function ?
Thanks

@spalger

This comment has been minimized.

Show comment
Hide comment
@spalger

spalger Apr 4, 2015

Member

@t0mst0ne absolutely. All of kibana's saved objects are just elasticsearch documents, and while they aren't always super easy to work with (since they have embedded json and such) you can absolutely modify the objects outside of kibana.

After creating the first search source you can take a look in the kibana index and find the saved object that's created – http://localhost:9200/.kibana/_search Then, you would just write a script that indexes documents just like it, but with modified kibanaSavedObjectMeta.searchSourceJSON values. The same is true for visualizations and dashboards. They are all just elasticsearch documents, but it might take a bit of reverse engineering.

Member

spalger commented Apr 4, 2015

@t0mst0ne absolutely. All of kibana's saved objects are just elasticsearch documents, and while they aren't always super easy to work with (since they have embedded json and such) you can absolutely modify the objects outside of kibana.

After creating the first search source you can take a look in the kibana index and find the saved object that's created – http://localhost:9200/.kibana/_search Then, you would just write a script that indexes documents just like it, but with modified kibanaSavedObjectMeta.searchSourceJSON values. The same is true for visualizations and dashboards. They are all just elasticsearch documents, but it might take a bit of reverse engineering.

@u238

This comment has been minimized.

Show comment
Hide comment
@u238

u238 commented Apr 10, 2015

+1

@ch40s

This comment has been minimized.

Show comment
Hide comment
@ch40s

ch40s Apr 16, 2015

+1000 :)

ch40s commented Apr 16, 2015

+1000 :)

@davidbono

This comment has been minimized.

Show comment
Hide comment
@davidbono

davidbono commented Apr 20, 2015

👍

@spalger spalger closed this in #3573 Apr 20, 2015

@mserdur

This comment has been minimized.

Show comment
Hide comment
@mserdur

mserdur commented Apr 22, 2015

+1

@Inderjeet26

This comment has been minimized.

Show comment
Hide comment
@Inderjeet26

Inderjeet26 commented Apr 23, 2015

+1

@ferranmunoz

This comment has been minimized.

Show comment
Hide comment
@ferranmunoz

ferranmunoz May 4, 2015

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

ferranmunoz commented May 4, 2015

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

@milanchandna

This comment has been minimized.

Show comment
Hide comment
@milanchandna

milanchandna May 13, 2015

+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.

milanchandna commented May 13, 2015

+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

This comment has been minimized.

Show comment
Hide comment
@ghost

ghost May 19, 2015

+1 Read it being available from 4.1.0 release

ghost commented May 19, 2015

+1 Read it being available from 4.1.0 release

@hex0cter

This comment has been minimized.

Show comment
Hide comment
@hex0cter

hex0cter commented May 26, 2015

+1

@nocturnal3d

This comment has been minimized.

Show comment
Hide comment
@nocturnal3d

nocturnal3d Jun 2, 2015

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

nocturnal3d commented Jun 2, 2015

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

@Guinoutortue

This comment has been minimized.

Show comment
Hide comment
@Guinoutortue

Guinoutortue Jun 2, 2015

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 :-( )

Guinoutortue commented Jun 2, 2015

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

This comment has been minimized.

Show comment
Hide comment
@jim-davis

jim-davis Jun 23, 2015

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

jim-davis commented Jun 23, 2015

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

This comment has been minimized.

Show comment
Hide comment
@ajay2881

ajay2881 Jun 24, 2015

Hi Jim, How to use the script?

ajay2881 commented Jun 24, 2015

Hi Jim, How to use the script?

@jim-davis

This comment has been minimized.

Show comment
Hide comment
@jim-davis

jim-davis Jun 24, 2015

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)

jim-davis commented Jun 24, 2015

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

This comment has been minimized.

Show comment
Hide comment
@ajay2881

ajay2881 Jun 25, 2015

Thanks Jim

ajay2881 commented Jun 25, 2015

Thanks Jim

@WCMinor

This comment has been minimized.

Show comment
Hide comment
@WCMinor

WCMinor Jul 15, 2015

+1 built in export/import

WCMinor commented Jul 15, 2015

+1 built in export/import

@carlosvega

This comment has been minimized.

Show comment
Hide comment
@carlosvega

carlosvega commented Jul 17, 2015

+1

@ddes

This comment has been minimized.

Show comment
Hide comment
@ddes

ddes commented Jul 27, 2015

+1

@EliasGoldberg

This comment has been minimized.

Show comment
Hide comment
@EliasGoldberg

EliasGoldberg commented Aug 13, 2015

+1

@wasmum

This comment has been minimized.

Show comment
Hide comment
@wasmum

wasmum commented Aug 26, 2015

+1

@wasmum

This comment has been minimized.

Show comment
Hide comment
@wasmum

wasmum Aug 26, 2015

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

wasmum commented Aug 26, 2015

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

This comment has been minimized.

Show comment
Hide comment
@lukasolson

lukasolson Aug 26, 2015

Member

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.

Member

lukasolson commented Aug 26, 2015

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

This comment has been minimized.

Show comment
Hide comment
@ShayanZafar

ShayanZafar commented Oct 14, 2015

+1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment