# Timestamp change pipeline

**URL:** <https://community.graylog.org/t/timestamp-change-pipeline/22212>\
**Category:** Graylog Central (peer support)\
**Created:** [January 1, 2022, 12:24pm UTC](https://community.graylog.org/t/timestamp-change-pipeline/22212 "2022-01-01T12:24:40Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**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:** [January 3, 2022, 11:57pm UTC](https://community.graylog.org/t/timestamp-change-pipeline/22212/2 "2022-01-03T23:57:38Z")

</div>

Hello,

Have you seen this.

> [@Timestamp Replacement Issues (Ingestion timestamp vs log timestamp)](https://community.graylog.org/t/timestamp-replacement-issues-ingestion-timestamp-vs-log-timestamp/9842/2):
>
> I did some troubleshooting and I can confirm that the pipeline is processing my messages, just isn’t doing what it’s supposed to do. I change my pipeline rule to set a static value for a field. rule “parse right timestamp” when has\_field(“timestamp\_orig”) then let new\_date = parse\_date(to\_string($message.timestamp\_orig)); set\_field(“beat\_hostname”, “taco”); end When I just change the set\_field to the variable it reverts back the hostname and not the time stamp. rule “par…

---

_[View the full topic](https://community.graylog.org/t/timestamp-change-pipeline/22212)._