# Filebeat 7.7.0 @timestamp not UTC

**URL:** <https://discuss.elastic.co/t/filebeat-7-7-0-timestamp-not-utc/235396>\
**Category:** Beats\
**Tags:** filebeat\
**Created:** [June 2, 2020, 6:50pm UTC](https://discuss.elastic.co/t/filebeat-7-7-0-timestamp-not-utc/235396 "2020-06-02T18:50:46Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![tzeappa](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tzeappa/32/69582_2.png) [@tzeappa](https://discuss.elastic.co/u/tzeappa)\
**Post date:** [June 2, 2020, 6:50pm UTC](https://discuss.elastic.co/t/filebeat-7-7-0-timestamp-not-utc/235396/1 "2020-06-02T18:50:46Z")

</div>

Hello,  
Since upgrading to Filebeat 7.7.0 it seems that the @timestamp is no longer UTC for `type: log` and it just parses the OS date without any timezone filtering.  
I have made sure that the `event.timezone` is added properly and I have set `var.convert_timezone: true` in filebeat but nothing seems to help.  
Does anyone has any idea on how I might resolved this issue?  
This looks like a regression bug that should be fixed as I have found articles describing older version doing this but usually it was resolved with `var.convert_timezone: true`.

Thank you!

---

<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:** [June 30, 2020, 6:51pm UTC](https://discuss.elastic.co/t/filebeat-7-7-0-timestamp-not-utc/235396/2 "2020-06-30T18:51:02Z")

</div>

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