Kibana map date format

Hi There ,

Im ingesting some 'date type' data using the following mapping properties.

"processed_date": {
        "type": "date",
        "format": "yyyy/MM/dd HH:mm:ss.SSSZZ||yyyy/MM/dd HH:mm:ss.SSS||yyyy/MM/dd"
      },

When looking at the json DEV response i see it correctly represented

"processed_date" : "2019/11/20 00:00:00.000",

it shows something like this : processed_date 1589241600000

v 7.11.1

Thank you

Jorge Vidinha

Tested in 7.13 (I can try later in 7.11) the following steps

  1. Create some sample data with your formatter, etc
PUT test_date
{
  "mappings": {
    "dynamic": false,
    "properties": {
      "location": {
        "type": "geo_point"
      },
      "processed_date": {
        "type": "date",
        "format": "yyyy/MM/dd HH:mm:ss.SSSZZ||yyyy/MM/dd HH:mm:ss.SSS||yyyy/MM/dd"
      }
    }
  }
}

POST test_date/_doc
{
  "location": [ -71.34, 41.12 ] ,
  "processed_date": "2019/11/20 00:00:00.000"
}

POST test_date/_doc
{
  "location": [ -70, 42 ] ,
  "processed_date": "2020/01/20 12:00:00.000"
}

POST test_date/_doc
{
  "location": [ -75, 32 ] ,
  "processed_date": "2020/01/27"
}
  1. Created the index pattern
  2. Created a new map with the data layer and everything seems fine

Have you tried Kibana field formatter in the index pattern? You can format the date the way you want it represented, for example:

... and Maps will honor that setting

Hope it helps!

This is a regression in 7.11, [Maps] Tooltips with timestamp appear as epoch · Issue #95072 · elastic/kibana · GitHub, that has been resolved in 7.12 and higher versions, [Maps] fix tooltips with timestamp appear as epoch by nreese · Pull Request #95106 · elastic/kibana · GitHub. You will need to upgrade to resolve the issue.

2 Likes

Thanks @jsanz , i was not aware of field formater , i tryed to make use of it but also did not work .. now we know why after @Nathan_Reese explanation ...
Thanks anyway for you time.

Regards

Thanks @Nathan_Reese , any great blog or advise on version upgrades .

Regards

Thanks @Nathan_Reese , Does that mean upgrading Kibana only to 7.13 would be sufficient ?
and staying with the elastic nodes at 7.11 ...

Since i plan to go with elastic cloud soon or later it would make things simpler for this on prem deployment im working at the moment ... thanks

It is advised to upgrade both elasticsearch and kibana to the same minor as kibana may request elasticsearch APIs specific to that minor version.

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