# Replacing default Graylog timestamp via Pipeline Processor

**URL:** <https://community.graylog.org/t/replacing-default-graylog-timestamp-via-pipeline-processor/9330>\
**Category:** Graylog Central (peer support)\
**Tags:** pipeline-rules, debuggingpl\
**Created:** [March 8, 2019, 10:17am UTC](https://community.graylog.org/t/replacing-default-graylog-timestamp-via-pipeline-processor/9330 "2019-03-08T10:17:35Z")\
**Posts on this page:** 1\
**Showing post:** 10

<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:** [March 11, 2019, 1:01pm UTC](https://community.graylog.org/t/replacing-default-graylog-timestamp-via-pipeline-processor/9330/10 "2019-03-11T13:01:33Z")

</div>

The following should do the trick

```auto
rule “replace timestamp”
when
    true
then
    let new_date = parse_date(to_string($message.http_time), “yyyy-MM-dd’T’HH:mm:ss”, "CET");
    set_field(“timestamp”, new_date);
end

```

You might want to add some debug information until it works like you expect. Something like you find in [Can't overwrite timestamp through pipeline-rule](https://community.graylog.org/t/cant-overwrite-timestamp-through-pipeline-rule/7445/5?u=jan)

---

_[View the full topic](https://community.graylog.org/t/replacing-default-graylog-timestamp-via-pipeline-processor/9330)._