Kibana Export and Import not working

Elastic Stack Kibana
1

Hi guys,

Exported some Kibana dashboards and vizualizations from one computer to another and I got the same error while importing the ndjson ==>

 Sorry, there was an error

The file could not be processed due to error: "Bad Request: Unexpected token [ in JSON at position 63"```

I am manually exporting them from one computer to another. How can I import all the dashboards from one comp to another?

Thank you!
2

It looks like your export file is corrupted. Can you provide the following information:

  • What do you mean by "computer"? Dashboards are saved in the Elasticsearch cluster connected to Kibana. If you want to transfer them from one cluster to another, then you need the export/import api. If you are connecting to the same cluster, this won't be necessary
  • What are the versions of Kibana you are using? Keep in mind you can't import an ndjson file exported from a more recent version of Kibana into an older Kibana version (the other way around will work fine)
  • Can you share the steps you perform to export, copy the ndjson file and import it again? Maybe some step in between is changing the contents somehow
  • Can you share the exported file itself?
3
  • What do you mean by "computer"? Dashboards are saved in the Elasticsearch cluster connected to Kibana. If you want to transfer them from one cluster to another, then you need the export/import api. If you are connecting to the same cluster, this won't be necessary

Answer: I have colleague A that is working on her own running ELK stack. She exported her dashboards from her own ELK stack via Kibana Import/Export, selected some dashboards and the ndjson generated by the tool was sent via email to colleague B that imported the json within his own ELK stack. No cluster involved, just separate ELks with only 1 node each.

  • What are the versions of Kibana you are using? Keep in mind you can't import an ndjson file exported from a more recent version of Kibana into an older Kibana version (the other way around will work fine)

Answer: 7.11.2 both

  • Can you share the steps you perform to export, copy the ndjson file and import it again? Maybe some step in between is changing the contents somehow
    Answer: see nr 1

  • Can you share the exported file itself? ==> Sorry I can't. But the export is from the tool via Kibana interface. No human interaction

4

I see, thanks for clearing that up. Unfortunately without the problematic file it's hard to give guidance here. You can also mask sensitive data.

6

I can't think of any settings that could cause this problem - it looks like the file itself is corrupted but I don't know how this could happen if it's just exported and imported via UI.

7

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