# Problelm with parsing a timestamp field

**URL:** <https://community.graylog.org/t/problelm-with-parsing-a-timestamp-field/31027>\
**Category:** Graylog Central (peer support)\
**Tags:** timestamp\
**Created:** [December 22, 2023, 4:54pm UTC](https://community.graylog.org/t/problelm-with-parsing-a-timestamp-field/31027 "2023-12-22T16:54:56Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![ramindia](https://sea2.discourse-cdn.com/flex016/user_avatar/community.graylog.org/ramindia/32/5085_2.png) [@ramindia](https://community.graylog.org/u/ramindia)\
**Post date:** [December 23, 2023, 3:29pm UTC](https://community.graylog.org/t/problelm-with-parsing-a-timestamp-field/31027/2 "2023-12-23T15:29:16Z")

</div>

> [@gdevelek](#):
>
> ailed to parse field [\_message\_timestamp] of type [date

check below thread help you

> [@Failed to parse date field](https://community.graylog.org/t/failed-to-parse-date-field/22411/3):
>
> Hey, thanks for your help! My input is GELF TCP, basically docker stderr forwarded by nxlog from the host. There were some random issues with docker logspout so we ended up with this arrangement. I don’t know if it would work better with Docker sending logs directly to Graylog with gelf but our Docker CE doesn’t support multiple drivers so that’s why we currently have this setup. I do have 1 extractor there which I believe is considered for the message as it contains string “alert” but it ha…

---

_[View the full topic](https://community.graylog.org/t/problelm-with-parsing-a-timestamp-field/31027)._