# Wrong timezone using haproxy module

**URL:** <https://discuss.elastic.co/t/wrong-timezone-using-haproxy-module/196368>\
**Category:** Beats\
**Tags:** beats-module, filebeat\
**Created:** [August 22, 2019, 4:43pm UTC](https://discuss.elastic.co/t/wrong-timezone-using-haproxy-module/196368 "2019-08-22T16:43:52Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![pcantea](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/pcantea/32/53396_2.png) [@pcantea](https://discuss.elastic.co/u/pcantea)\
**Post date:** [August 22, 2019, 4:43pm UTC](https://discuss.elastic.co/t/wrong-timezone-using-haproxy-module/196368/1 "2019-08-22T16:43:52Z")

</div>

I have the same issue as [[Still Not Solved!] Filebeat cannot recognize timezone in syslog](https://discuss.elastic.co/t/still-not-solved-filebeat-cannot-recognize-timezone-in-syslog/192661)

HAProxy logs have the correct date on the server, the server timezone is set to UTC-8 (Pacific), but the timestamp being sent to elasticsearch doesn't have the timezone info.

e.g this log file entry was generated at 9:39am PDT  
"@timestamp": "2019-08-22T09:39:29.445Z",

---

<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:** [September 19, 2019, 4:44pm UTC](https://discuss.elastic.co/t/wrong-timezone-using-haproxy-module/196368/2 "2019-09-19T16:44:05Z")

</div>

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