# FortiGate and timezone settings

**URL:** <https://community.graylog.org/t/fortigate-and-timezone-settings/19054>\
**Category:** Graylog Central (peer support)\
**Created:** [March 10, 2021, 7:13am UTC](https://community.graylog.org/t/fortigate-and-timezone-settings/19054 "2021-03-10T07:13:59Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![Tuumke](https://sea2.discourse-cdn.com/flex016/user_avatar/community.graylog.org/tuumke/32/2549_2.png) [@Tuumke](https://community.graylog.org/u/Tuumke)\
**Post date:** [March 10, 2021, 7:40am UTC](https://community.graylog.org/t/fortigate-and-timezone-settings/19054/2 "2021-03-10T07:40:40Z")

</div>

Figured it out. In the syslog message from the fortgate there is a TZ field which is set to +0100. I guess graylog doesn’t automaticly recognize it. So i did the pipeline suggestion in [here](https://community.graylog.org/t/fortigate-changed-eventtime-from-seconds-to-nanoseconds/18772/2).

All works out now.

---

_[View the full topic](https://community.graylog.org/t/fortigate-and-timezone-settings/19054)._