# High resolution "sort by" in Kibana \>Discover

**URL:** https://discuss.elastic.co/t/high-resolution-sort-by-in-kibana-discover/171364
**Category:** Kibana
**Created:** [March 7, 2019, 5:50pm UTC](https://discuss.elastic.co/t/high-resolution-sort-by-in-kibana-discover/171364 "2019-03-07T17:50:19Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![BKG](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/bkg/32/43591_2.png) [@BKG](https://discuss.elastic.co/u/BKG)
#### Post date: [March 7, 2019, 5:50pm UTC](https://discuss.elastic.co/t/high-resolution-sort-by-in-kibana-discover/171364/1 "2019-03-07T17:50:19Z")

</div>

Hi,

We have some very verbose logs down to microsecond resolution. Our timestamp is the following format:

`YYYY-MM-DD HH:mm:ss.SSSSSS`

I have passed everything except the last three SSS to date{} to override `@timestamp`, which works, however I am seeing logs out of order.

I then had my devs add a microseconds field to the logs with the plan on converting it to a number field then being able to sort on it, however timestamps that look like this: `1919031265000000` don't fit in an int, and I just found out long isn't supported by `mutate->convert`.

What can I do in this situation?

Thanks

---

<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: [April 4, 2019, 5:50pm UTC](https://discuss.elastic.co/t/high-resolution-sort-by-in-kibana-discover/171364/2 "2019-04-04T17:50:22Z")

</div>

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