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

Cannot import settings from Kibana #10250

Closed
thedatamachine opened this issue Feb 8, 2017 · 3 comments
Closed

Cannot import settings from Kibana #10250

thedatamachine opened this issue Feb 8, 2017 · 3 comments
Labels
feedback_needed notabug When the issue is closed this label Indicates that it wasn't a bug

Comments

@thedatamachine
Copy link

Kibana version:4.1.1

Elasticsearch version:1.7.3

Server OS version:osx 10.11.6

Browser version:chrome 54.0.2840.98 (64-bit)

Browser OS version:osx 10.11.6

Original install method (e.g. download page, yum, from source, etc.):download

Description of the problem including expected versus actual behavior:
Export settings from a Kibana4.1.1/ES1.7.3 installation (see attached json), import those settings to a new Kibana4.1.1/ES1.7.3. An error occurs (see screenshot)

export (2).json.zip

screen shot 2017-02-08 at 12 21 53 pm

Steps to reproduce:
1.
2.
3.

Errors in browser console (if relevant):

Provide logs and/or server output (if relevant):

Describe the feature:

@tbragin
Copy link
Contributor

tbragin commented Feb 13, 2017

Looks like it's looking for a saved search named "QA-Search-Failure" to which the "QA-Search-Failures" refers to. And that saved search is not in the JSON you provided.

  {
    "_id": "QA-Search-Failures",
    "_type": "visualization",
    "_source": {
      "title": "QA Search Failures",
      "visState": "{\"type\":\"metric\",\"params\":{\"fontSize\":60},\"aggs\":[{\"id\":\"1\",\"type\":\"count\",\"schema\":\"metric\",\"params\":{}}],\"listeners\":{}}",
      "description": "",
      "savedSearchId": "QA-Search-Failure",
      "version": 1,
      "kibanaSavedObjectMeta": {
        "searchSourceJSON": "{\"filter\":[]}"
      }
    }
  },

Are you sure this is a full export from the previous system, including all the saved searches?

@tbragin tbragin added feedback_needed notabug When the issue is closed this label Indicates that it wasn't a bug labels Feb 13, 2017
@thedatamachine
Copy link
Author

thedatamachine commented Mar 28, 2017

Hello, I had to break away from this problem, but am back working on it again.
Actually, the saved search object "QA-Search-Failure" is present in the json file at line 125.

Today I tried the export/import again and I am seeing this failure:
Error: Could not locate that search (id: QA-Index-success)
at SavedObject.self.applyESResp (http://localhost:5601/index.js?_b=7668:91145:54)
at wrappedCallback (http://localhost:5601/index.js?_b=7668:20893:81)
at http://localhost:5601/index.js?_b=7668:20979:26
at Scope.$eval (http://localhost:5601/index.js?_b=7668:22022:28)
at Scope.$digest (http://localhost:5601/index.js?_b=7668:21834:31)
at Scope.$apply (http://localhost:5601/index.js?_b=7668:22126:24)
at done (http://localhost:5601/index.js?_b=7668:17661:45)
at completeRequest (http://localhost:5601/index.js?_b=7668:17875:7)
at XMLHttpRequest.xhr.onreadystatechange (http://localhost:5601/index.js?_b=7668:17814:11)

The saved search object is present in the newly attached json at line 272.

export (3).json.zip

@w33ble
Copy link
Contributor

w33ble commented Mar 31, 2017

This is almost certainly caused by #7667, which is closed by #10740.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feedback_needed notabug When the issue is closed this label Indicates that it wasn't a bug
Projects
None yet
Development

No branches or pull requests

3 participants