# Filebeat 7.3 Timezone Issues with System Module

**URL:** <https://discuss.elastic.co/t/filebeat-7-3-timezone-issues-with-system-module/195971>\
**Category:** Beats\
**Tags:** filebeat\
**Created:** [August 20, 2019, 4:09pm UTC](https://discuss.elastic.co/t/filebeat-7-3-timezone-issues-with-system-module/195971 "2019-08-20T16:09:09Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![Kent\_Wang](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kent_wang/32/52610_2.png) [@Kent\_Wang](https://discuss.elastic.co/u/Kent_Wang)\
**Post date:** [August 21, 2019, 3:51am UTC](https://discuss.elastic.co/t/filebeat-7-3-timezone-issues-with-system-module/195971/5 "2019-08-21T03:51:45Z")

</div>

I have the same problem, and I submited a fix here. Hope that helps.

> [@Filebeat 7.3 syslog / auth log timezone parsing error](https://discuss.elastic.co/t/filebeat-syslog-auth-log-timezone-parsing-error/196031):
>
> Hi Guys, I think there is something wrong in the system module ingest pipeline related to timezone processing. Here is an excerpt of date processors from pipipeline.json: { "date": { "field": "system.auth.timestamp", "target\_field": "@timestamp", "formats": ["MMM d HH:mm:ss", "MMM dd HH:mm:ss", "ISO8601"], "ignore\_failure": true } }, { "date": { "if": "ctx.event.timezone != null", "field…

---

_[View the full topic](https://discuss.elastic.co/t/filebeat-7-3-timezone-issues-with-system-module/195971)._