# Streams Graylog

**URL:** <https://community.graylog.org/t/streams-graylog/1393>\
**Category:** Graylog Central (peer support)\
**Created:** [June 9, 2017, 5:11am UTC](https://community.graylog.org/t/streams-graylog/1393 "2017-06-09T05:11:06Z")\
**Posts on this page:** 1\
**Showing post:** 22

<div class="post-metadata">

**Author:** ![jan](https://sea2.discourse-cdn.com/flex016/user_avatar/community.graylog.org/jan/32/11_2.png) [@jan](https://community.graylog.org/u/jan)\
**Post date:** [June 14, 2017, 3:06pm UTC](https://community.graylog.org/t/streams-graylog/1393/22 "2017-06-14T15:06:03Z")

</div>

The explanation is:

> [@Flexibly Parse Date](https://community.graylog.org/t/flexibly-parse-date/1440/6):
>
> timestamp is a non-string field (it contains a Date object), so extractors won’t run on that. Either use processing pipeline rules and the parse\_date() function or try extracting the timestamp from your message or full\_message fields as a string (using a Regex extractor and a Date converter).

---

_[View the full topic](https://community.graylog.org/t/streams-graylog/1393)._