# Nanosecond support in Logs UI **URL:** https://discuss.elastic.co/t/nanosecond-support-in-logs-ui/261048 **Category:** Logs **Created:** [January 13, 2021, 8:27pm UTC](https://discuss.elastic.co/t/nanosecond-support-in-logs-ui/261048 "2021-01-13T20:27:36Z") **Posts on this page:** 1 **Showing post:** 3
### Author: ![juan.domenech](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/juan.domenech/32/142257_2.png) [@juan.domenech](https://discuss.elastic.co/u/juan.domenech) #### Post date: [January 24, 2021, 12:58pm UTC](https://discuss.elastic.co/t/nanosecond-support-in-logs-ui/261048/3 "2021-01-24T12:58:02Z")
I found the same issue while indexing on nanoseconds. My work around to keep Logs UI working is to **include two timestamps in the events** : The standard @timestamp in milliseconds and a second one @timestamp\_nanoseconds. I made @timestamp\_nanoseconds the **Time Field in the Index Pattern** and this allows Discovery to use nanoseconds. While at the same time Logs UI is happy when it finds @timestamp. [Some details over here.](https://discuss.elastic.co/t/how-to-index-nanoseconds-precision-events-with-logstash-7-10-and-type-date-nanos/262029) I hope it helps. --- _[View the full topic](https://discuss.elastic.co/t/nanosecond-support-in-logs-ui/261048)._