Failed to find Kibana 5 data.

Question

I created an Amazon Elasticsearch test service that uses Elastic and Kibana 5.1.

I can insert a test entry through curl:

curl -XPOST "https://mytestservicedomain.amazonaws.com/testindex/testtype" -d "{\"foo\":\"bar\"}" 

And make sure it was inserted using Kibana Dev tools:

Request:

 GET _search { "query": { "match_all": {} } } 

Answer:

 { "_index": "testindex", "_type": "testtype", "_id": "AVoQD4Kyv413fK4nN1sg", "_score": 1, "_source": { "foo": "bar" } } 

But when I go to Discover in the Kibana menu, I can’t get any results. All I get are a few errors:

• Saved "field" parameter is now invalid. Please select a new field.
• Discover: "field" is a required parameter

I found a couple of posts ( post 1 , post 2 ) on the Elastic Forums that seem to suggest Kibana / Elastic compatibility issues, but I just wanted to see if anyone else was working.

Answer 1

in my case: update and transfer data from moose (2 + versino) to moose (5.4). everything is fine, except for the "Discover:" field - a required parameter

then I delete the index in Management / Kibana , read it, still not working

Finally, I found, I have to share the old .kibana index in ES, so I just

curl -XDELETE myesdomain.com:9200/.kibana

or use Dev ToolS DELETE /.kibana

Answer 2

I hit my head on the table because of this problem. I don’t know exactly what the problem is, but I can tell you what I did to solve this problem. I deleted the index template that generated the error and recreated it with the check "The index contains time-dependent events", I gave it the same name / regular expression as before (the same as I deleted), and set " Time- field name "for a specific record, and then updated kibanu. In my case, I had computer events stored in an elastic state, and each of the documents had “insert_date”, which was the field that I selected as “Time field name”. I don't know how much this will help you, but it worked for me, at least for most index templates. I still have a couple of index templates that still generate the above error despite deleting and re-creating. Therefore, my solution does not work in all cases, and I am curious to find what is connected with them.

Answer 3

I was struck by this problem over the past week. I was so confused and linked to the git hub error page. accidentally found a solution to this error. When we add an index to kibana through the control settings, we need to specify a specific field in the "Fields to update the temporary field name" field. This is a field that you should carefully check. You must choose which field is present in your document as a required field or a field that exists throughout the document. Once this is correctly matched, the error will disappear and you will be able to see your index document. Good coding.