# Double convert timezone when parse datetime from sql

**URL:** <https://discuss.elastic.co/t/double-convert-timezone-when-parse-datetime-from-sql/177646>\
**Category:** Logstash\
**Created:** [April 19, 2019, 4:08pm UTC](https://discuss.elastic.co/t/double-convert-timezone-when-parse-datetime-from-sql/177646 "2019-04-19T16:08:42Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![Badger](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/badger/32/25190_2.png) [@Badger](https://discuss.elastic.co/u/Badger)\
**Post date:** [April 19, 2019, 4:52pm UTC](https://discuss.elastic.co/t/double-convert-timezone-when-parse-datetime-from-sql/177646/2 "2019-04-19T16:52:57Z")

</div>

You might be able to fix it like [this](https://discuss.elastic.co/t/error-logstash-inputs-jdbc-unable-to-connect-to-database/177091/4?u=badger). Or you could add a timezone option to the date filter to force it to move the timestamp forward three hours.

---

_[View the full topic](https://discuss.elastic.co/t/double-convert-timezone-when-parse-datetime-from-sql/177646)._
