# Filebeat incorrect timestamp

**URL:** <https://discuss.elastic.co/t/filebeat-incorrect-timestamp/189009>\
**Category:** Beats\
**Tags:** filebeat\
**Created:** [July 5, 2019, 6:06am UTC](https://discuss.elastic.co/t/filebeat-incorrect-timestamp/189009 "2019-07-05T06:06:20Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![Marct](https://avatars.discourse-cdn.com/v4/letter/m/c57346/32.png) [@Marct](https://discuss.elastic.co/u/Marct)\
**Post date:** [July 6, 2019, 6:00pm UTC](https://discuss.elastic.co/t/filebeat-incorrect-timestamp/189009/3 "2019-07-06T18:00:33Z")

</div>

Thanks for the answer, the raw logs received in to ES were in my local timezone, but ES what I think was happening was ES assumed they were UTC and added +2 hours when storing them which meant I could not see any data unless I moved the time scale 2 hours forward.

After modifying the `manifest.yml` file in the panw modules folder to the following everything seemed to resolve and the logs and timestamps are now correct

`- name: convert_timezone`  
`default: true`

---

_[View the full topic](https://discuss.elastic.co/t/filebeat-incorrect-timestamp/189009)._