You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I came here from elastic/kibana#11632 looking for a way to export from one Kibana and import to another. The import using this tool to an empty (ie, there are no .kibana/saved_objects) elasticsearch runs okay, however it leaves the interlinking IDs inconsistent. Dashboards should point to visualizations, which point to searches, which point to indexes. All of those pointers ought be hooked up in the new elasticsearch. I'm in 5.6.4 for both, if that matters.
Is this understanding about right?
If so I can work on a fix, which might go like this (if also sounding about right?)
post all the saved searches from the loaded objects, recording their old and new IDs
post all the visualizations from the loaded objects, doing the mapping from (1), and recording old and new IDs.
post all the dashboards from the loaded objects, using the mapping from (2)
The text was updated successfully, but these errors were encountered:
Update - I can correct my understanding - since kibana-importer is using &overwrite=true, the ID gap is limited to the imported objects pointing to the defaultIndex, which will probably have a different ID. My updated fix then involves asking kibana for its new defaultIndex ID and only touching the object fields that point to that. I'll do a PR in case it helps someone else.
I came here from elastic/kibana#11632 looking for a way to export from one Kibana and import to another. The import using this tool to an empty (ie, there are no .kibana/saved_objects) elasticsearch runs okay, however it leaves the interlinking IDs inconsistent. Dashboards should point to visualizations, which point to searches, which point to indexes. All of those pointers ought be hooked up in the new elasticsearch. I'm in 5.6.4 for both, if that matters.
Is this understanding about right?
If so I can work on a fix, which might go like this (if also sounding about right?)
The text was updated successfully, but these errors were encountered: