I have successfully set up a Kibana 4.x dashboard along with Elasticsearch 2.x, but I feel 5.x versions should be the future-proof way to go. However for some reason Kibana fails to recognize any field types when trying to visualize data, although it correctly shows types on settings and discovery views.
Prior questions on this seemed to be about geo_point
types but here I'm just hoping to use basic numeric and non-analyzed string fields.
Both are running in a Docker container without any modifications to settings, FROM: kibana:5
and FROM: elasticsearch:5
. I only have one index on this Poc Elasticsearch instance and it has an explicit mapping of types. I assume this configuration works for ES 5.x as well as for 2.x:
{
"mappings": {
"entry": {
"_source": {
"enabled": true
},
"properties": {
"times": {
"type": "float"
},
"tot_calls": {
"type": "integer"
},
"time": {
"type": "float"
},
"datetime": {
"type": "date",
"format": "YYYY-MM-dd HH:mm:ssZ"
},
"datetime_num": {
"type": "long"
},
"env": {
"type": "string",
"index": "not_analyzed",
"norms": {
"enabled": false
}
},
"ip": {
"type": "ip"
},
"day": {
"type": "integer"
},
"tags": {
"type": "string",
"index": "not_analyzed",
"norms": {
"enabled": false
}
},
"name": {
"type": "string",
"index": "not_analyzed",
"norms": {
"enabled": false
}
},
"tot_times": {
"type": "float"
}
},
"_all": {
"enabled": false
}
}
},
"settings": {
"number_of_shards": 3,
"number_of_replicas": 0
}
}
At least _source
looks valid on stored documents. Any tips on how to resolve this would be welcome! The status on different views: