Upgrade 6.4.0->6.5.1 or .2 loses time field on some Kibana index patterns

Elastic Stack Kibana
1

We've just upgraded ES/Kibana in our dev environments, and on both my laptop and our two-node dev cluster, we've noticed that some index patterns in Kibana have lost the notion of their time field. The fields themselves still exist in the indices. Here are two examples from different indices (actually they were set up referring to aliases) one which worked, one didn't; both used a field other than @timestamp for their time:

{
    "_id": "cb2cbb80-d08e-11e8-92c6-75f92827682b",
    "_type": "index-pattern",
    "_source": {
        "title": "xxx-event",
        "fields": "[{\"name\":\"@timestamp\",\"type\":\"date\", ...]"
},

vs

{
    "_id": "06243660-e2b3-11e8-b7f2-072667ac6ffb",
    "_type": "index-pattern",
    "_source": {
        "title": "yyy-events",
        "timeFieldName": "final.time",
        "fields": "[{\"name\":\"@timestamp\",\"type\":\"date\", ...]"
},

There was nothing related to these in the Kibana or ES logs. Any thoughts on

  • How that happened, and how to avoid it
  • How to reinstate the time field (best I can see right now is export json, hand-edit, reimport)
2

Hmm, I'm not sure what happened here. Have you tried again and seen the same problem?

3

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