# Overriding timestamp, now logs are out of order
**URL:** https://discuss.elastic.co/t/overriding-timestamp-now-logs-are-out-of-order/170720
**Category:** Logstash
**Created:** [March 4, 2019, 11:50am UTC](https://discuss.elastic.co/t/overriding-timestamp-now-logs-are-out-of-order/170720 "2019-03-04T11:50:37Z")
**Posts on this page:** 3
**Page:** 1
### Author:  [@BKG](https://discuss.elastic.co/u/BKG)
#### Post date: [March 4, 2019, 11:50am UTC](https://discuss.elastic.co/t/overriding-timestamp-now-logs-are-out-of-order/170720/1 "2019-03-04T11:50:37Z")
Hi All,
I have successfully extracted our date and used it to override the @timestamp, however because our application uses microseconds and Elasticsearch only supports milliseconds, my logs for some events are now appearing out of order.
I've stored microseconds in a separate field, however I am aware it's not currently possible to view the logs in any other order in Kibana \> Discover than timestamp, my question is. Is there a way I can use the log order or my microseconds field as a secondary sort field at the Logstash level before the logs are transmitted?
Thanks!
---
### Author:  [@BKG](https://discuss.elastic.co/u/BKG)
#### Post date: [March 6, 2019, 11:22am UTC](https://discuss.elastic.co/t/overriding-timestamp-now-logs-are-out-of-order/170720/2 "2019-03-06T11:22:36Z")
Does anyone have any idea how to get around this issue?
Thanks
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [April 3, 2019, 11:22am UTC](https://discuss.elastic.co/t/overriding-timestamp-now-logs-are-out-of-order/170720/3 "2019-04-03T11:22:37Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.