# Set kibana to use more decimal places of millisencond of time field

**URL:** https://discuss.elastic.co/t/set-kibana-to-use-more-decimal-places-of-millisencond-of-time-field/274850
**Category:** Kibana
**Created:** [June 3, 2021, 10:20am UTC](https://discuss.elastic.co/t/set-kibana-to-use-more-decimal-places-of-millisencond-of-time-field/274850 "2021-06-03T10:20:41Z")
**Posts on this page:** 4
**Page:** 1

<div class="post-metadata">

### Author: ![sosogh](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/sosogh/32/78055_2.png) [@sosogh](https://discuss.elastic.co/u/sosogh)
#### Post date: [June 3, 2021, 10:20am UTC](https://discuss.elastic.co/t/set-kibana-to-use-more-decimal-places-of-millisencond-of-time-field/274850/1 "2021-06-03T10:20:41Z")

</div>

The log record displaying order in kibana discover is from lastest to the oldest .

The millisencond of time field is six decimal places , but it seems that kibana only use three ?

```json
{
  "_index": "btcs-all-in-one-000004",
  "_type": "_doc",
  "_id": "Uj1S0XkB5s4UegPPCtF5",
  "_version": 1,
  "_score": null,
  "_source": {
    "message": "2021-06-03 18:01:24.0560 [taskScheduler-4] INFO c.d.b.s.s.impl.DealVehicleSevice 21",
    "fulltime": "2021-06-03T10:01:24.056000Z",
    "service_name": "schedule",
    "log_level": "info"
  },
  "fields": {
    "fulltime": [
      "2021-06-03T10:01:24.056Z"
    ]
  },
  "sort": [
    1622714484056
  ]
}

{
  "_index": "btcs-all-in-one-000004",
  "_type": "_doc",
  "_id": "Uz1S0XkB5s4UegPPCtF5",
  "_version": 1,
  "_score": null,
  "_source": {
    "message": "2021-06-03 18:01:24.0561 [taskScheduler-4] INFO c.d.b.s.s.impl.DealVehicleSevice 219",
    "fulltime": "2021-06-03T10:01:24.056100Z",
    "service_name": "schedule",
    "log_level": "info"
  },
  "fields": {
    "fulltime": [
      "2021-06-03T10:01:24.056Z"
    ]
  },
  "sort": [
    1622714484056
  ]
}

```

So some log records will be displayed in the wrong order ?

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/8/9/891be91e05c1d799e7d28f5163f2deaa83ce6a11.jpeg)

My question is that :  
Can it be set to use six decimal places of the millisencond of time field  
Thank you

---

<div class="post-metadata">

### Author: ![flash1293](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/flash1293/32/41227_2.png) [@flash1293](https://discuss.elastic.co/u/flash1293)
#### Post date: [June 3, 2021, 12:06pm UTC](https://discuss.elastic.co/t/set-kibana-to-use-more-decimal-places-of-millisencond-of-time-field/274850/2 "2021-06-03T12:06:52Z")

</div>

Is `fulltime` declared as a date field in the mapping? [Date field type | Elasticsearch Guide [7.13] | Elastic](https://www.elastic.co/guide/en/elasticsearch/reference/current/date.html)

If yes, then this is the expected behavior, as a `date` field can't exceed millisecond precision. If you want to go further than that, please use `date_nanos` instead: [Date nanoseconds field type | Elasticsearch Guide [master] | Elastic](https://www.elastic.co/guide/en/elasticsearch/reference/master/date_nanos.html)

---

<div class="post-metadata">

### Author: ![sosogh](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/sosogh/32/78055_2.png) [@sosogh](https://discuss.elastic.co/u/sosogh)
#### Post date: [June 4, 2021, 1:17am UTC](https://discuss.elastic.co/t/set-kibana-to-use-more-decimal-places-of-millisencond-of-time-field/274850/3 "2021-06-04T01:17:59Z")

</div>

I got it , thank you .

---

<div class="post-metadata">

### Author: ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)
#### Post date: [July 2, 2021, 1:18am UTC](https://discuss.elastic.co/t/set-kibana-to-use-more-decimal-places-of-millisencond-of-time-field/274850/4 "2021-07-02T01:18:46Z")

</div>

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