# Wrong timestamp in Alerting new elastic

**URL:** <https://discuss.elastic.co/t/wrong-timestamp-in-alerting-new-elastic/321286>\
**Category:** Kibana\
**Tags:** elastic-stack-alerting\
**Created:** [December 15, 2022, 10:09am UTC](https://discuss.elastic.co/t/wrong-timestamp-in-alerting-new-elastic/321286 "2022-12-15T10:09:13Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![diegomarting](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/diegomarting/32/99596_2.png) [@diegomarting](https://discuss.elastic.co/u/diegomarting)\
**Post date:** [December 15, 2022, 10:09am UTC](https://discuss.elastic.co/t/wrong-timestamp-in-alerting-new-elastic/321286/1 "2022-12-15T10:09:13Z")

</div>

Hello,  
I am migrating some alerts to te new version of Elastic Stack. I created the rules and the actions to send a message to a Google Webhook when an error log is ingested, but when I formatted the message with the mustache variables I don't get the right timestamp (The message shows the timestamp for time zone GMT+-0, and I am in GMT+1). I tried to change the format, but no solution was reached. Is there any way to configure the time zone to show the right timestamp of my city??

Thank you 🙂

---

<div class="post-metadata">

**Author:** ![Patrick\_Mueller](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/patrick_mueller/32/109425_2.png) [@Patrick\_Mueller](https://discuss.elastic.co/u/Patrick_Mueller)\
**Post date:** [December 15, 2022, 7:18pm UTC](https://discuss.elastic.co/t/wrong-timestamp-in-alerting-new-elastic/321286/2 "2022-12-15T19:18:56Z")

</div>

Sorry, we don't have anything to help for this today. We've played with a few ideas mentioned in this issue: [[alerts] provide mustache functions for ease-of-use in transforming mustache variables · Issue #84217 · elastic/kibana · GitHub](https://github.com/elastic/kibana/issues/84217) - I'd guess once we implement something to help in this area, we'll notify back in that issue. In case you'd like to track the progress.

I believe some folks have worked around this by using our webhook connector to connect to some webhook they've implemented, to format the data the way they want, invoke their own services, etc.

---

<div class="post-metadata">

**Author:** ![diegomarting](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/diegomarting/32/99596_2.png) [@diegomarting](https://discuss.elastic.co/u/diegomarting)\
**Post date:** [December 16, 2022, 1:35pm UTC](https://discuss.elastic.co/t/wrong-timestamp-in-alerting-new-elastic/321286/3 "2022-12-16T13:35:07Z")

</div>

Thank you Patrick for the fast anwer.

I will be tracking the issue and waiting for the new updates 🙂

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [January 13, 2023, 12:09pm UTC](https://discuss.elastic.co/t/wrong-timestamp-in-alerting-new-elastic/321286/4 "2023-01-13T12:09:13Z")

</div>



---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [February 10, 2023, 12:10pm UTC](https://discuss.elastic.co/t/wrong-timestamp-in-alerting-new-elastic/321286/5 "2023-02-10T12:10:13Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.