# Issues with date type converter format string **URL:** \ **Category:** Graylog Central (peer support)\ **Created:** [October 21, 2021, 9:49am UTC](https://community.graylog.org/t/issues-with-date-type-converter-format-string/21524 "2021-10-21T09:49:57Z")\ **Posts on this page:** 1\ **Showing post:** 11
**Author:** ![gsmith](https://sea2.discourse-cdn.com/flex016/user_avatar/community.graylog.org/gsmith/32/1222_2.png) [@gsmith](https://community.graylog.org/u/gsmith)\ **Post date:** [October 28, 2021, 4:46am UTC](https://community.graylog.org/t/issues-with-date-type-converter-format-string/21524/11 "2021-10-28T04:46:11Z")
Not sure if this helps, but I came across this post earlier today with a similar issue with Nginx > [@Graylog exctractor specify timezone other than UTC](https://community.graylog.org/t/graylog-exctractor-specify-timezone-other-than-utc/3663): > > Hello team! I have a message with timestamp without specified timezone in it, but timezone actually -6 CST. It is not UTC. Message: “2017/12/30 15:19:57 [error] 27739#0: \*3722503 limiting requests, excess: 0.062 by zone “wp-login”, client: 10.189.252.6, server: [blog.com](http://blog.com), request: “POST /ame/wp-login.php HTTP/1.1”, host: “[www.ame.com](http://www.ame.com)”” With following GROK pattern: %{DATESTAMP\_EVENTLOG:timestamp;date;yyyy/MM/dd HH:mm:ss} Is there a way to specify at time parsing tell that timestamp in messag… --- _[View the full topic](https://community.graylog.org/t/issues-with-date-type-converter-format-string/21524)._