# Log sequence issue in Kibana 6.4.2 **URL:** \ **Category:** Kibana\ **Created:** [May 7, 2019, 5:09am UTC](https://discuss.elastic.co/t/log-sequence-issue-in-kibana-6-4-2/179884 "2019-05-07T05:09:39Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![premchand](https://avatars.discourse-cdn.com/v4/letter/p/bcef8e/32.png) [@premchand](https://discuss.elastic.co/u/premchand)\ **Post date:** [May 7, 2019, 5:09am UTC](https://discuss.elastic.co/t/log-sequence-issue-in-kibana-6-4-2/179884/1 "2019-05-07T05:09:39Z")
All, We are successfully shipping logs to ELK using Python script and app log is created. We have created a JSON index in Kibana to search the log. Actual App Logs are generating in Kibana but with different sequence. We have cross-checked logship.ini and found out that there is some problem with Kibana reading milliseconds of the Actual log file. We have used UTC=True but date parsing is not happening for milliseconds, instead it takes 000Z. Any suggestion pls. ---
**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\ **Post date:** [May 7, 2019, 5:46am UTC](https://discuss.elastic.co/t/log-sequence-issue-in-kibana-6-4-2/179884/2 "2019-05-07T05:46:59Z")
Are you indexing directly into Elasticsearch from your Python application? What does a sample JSON document look like if you open the discover tab? ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [June 4, 2019, 5:47am UTC](https://discuss.elastic.co/t/log-sequence-issue-in-kibana-6-4-2/179884/3 "2019-06-04T05:47:04Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.