Home‎ > ‎

Kibana rounding to 16 significant digits

posted Apr 7, 2016, 10:00 AM by Allen Gattis   [ updated Apr 7, 2016, 10:01 AM ]
Turns out, if you have a value of type integer, that's just the limit. While elasticsearch shows you this:

curl http://localhost:9200/logstash-db-2016/isim-process/8163783564660983218?pretty
{
  "_index" : "logstash-db-2016",
  "_type" : "isim-process",
  "_id" : "8163783564660983218",
  "_version" : 1,
  "found" : true,
  "_source":{"requester_name":"8163783564660983218","request_num":8163783618037078861,"started":"2016-04-07 15:16:16:139 GMT","completed":"2016-04-07 15:16:16:282 GMT","subject_service":"Service","request_type":"EP","result_summary":"AA","requestee_name":"Mr. Requester","subject":"mrRequest","@version":"1","@timestamp":"2016-04-07T15:16:16.282Z"}
}

Kibana shows you this



View: Table / JSON / Raw
FieldActionValue



request_num  8163783618037079000




Looking at the JSON will give you the clue - it's being treated as an integer and not a string.


"_source": { "requester_name": "8163783564660983218", "request_num": 8163783618037079000, "started": "2016-04-07 15:16:16:139 GMT", "completed": "2016-04-07 15:16:16:282 GMT",


Mutate it to string in logstash to get your precision back.

https://github.com/elastic/kibana/issues/4356

Comments