# Filebeat syslog with wrong @timestamp

**URL:** <https://discuss.elastic.co/t/filebeat-syslog-with-wrong-timestamp/195454>\
**Category:** Beats\
**Tags:** filebeat\
**Created:** [August 16, 2019, 8:29am UTC](https://discuss.elastic.co/t/filebeat-syslog-with-wrong-timestamp/195454 "2019-08-16T08:29:25Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![ntlong](https://avatars.discourse-cdn.com/v4/letter/n/ce73a5/32.png) [@ntlong](https://discuss.elastic.co/u/ntlong)\
**Post date:** [August 16, 2019, 8:29am UTC](https://discuss.elastic.co/t/filebeat-syslog-with-wrong-timestamp/195454/1 "2019-08-16T08:29:26Z")

</div>

Hi everyone,

I am very new with all of elastic stack, so i hope that you guy can help in details.  
I am trying to configure filebeat to send syslog directly to elasticsearch, however, the @timestamp of each entry seem to have wrong timezone (+7 hours compare with locace time of server)  
I have done some research and test with below setting but that not have to resolve the problem:

- Stop filebeat
- add var.convert\_timezone: true in system.yml
- delete the current pipeline: curl -XDELETE '[http://localhost:9200/\_ingest/pipeline/filebeat-6.3.1-system-syslog-pipeline](http://localhost:9200/_ingest/pipeline/filebeat-6.3.1-system-syslog-pipeline)
- Start filebeat.

The strange things is I have metricbeat deployed in the same system but @timestamp is correct.

I am really in need of your suggestion.

Thank you all!

---

<div class="post-metadata">

**Author:** ![ntlong](https://avatars.discourse-cdn.com/v4/letter/n/ce73a5/32.png) [@ntlong](https://discuss.elastic.co/u/ntlong)\
**Post date:** [August 16, 2019, 8:36am UTC](https://discuss.elastic.co/t/filebeat-syslog-with-wrong-timestamp/195454/2 "2019-08-16T08:36:53Z")

</div>

If you guy need any information or any configuration, please suggest and i will share the details.

---

<div class="post-metadata">

**Author:** ![admlko](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/admlko/32/21787_2.png) [@admlko](https://discuss.elastic.co/u/admlko)\
**Post date:** [August 16, 2019, 9:34am UTC](https://discuss.elastic.co/t/filebeat-syslog-with-wrong-timestamp/195454/3 "2019-08-16T09:34:09Z")

</div>

Have you seen this: [[Still Not Solved!] Filebeat cannot recognize timezone in syslog](https://discuss.elastic.co/t/still-not-solved-filebeat-cannot-recognize-timezone-in-syslog/192661/20)

---

<div class="post-metadata">

**Author:** ![ntlong](https://avatars.discourse-cdn.com/v4/letter/n/ce73a5/32.png) [@ntlong](https://discuss.elastic.co/u/ntlong)\
**Post date:** [August 17, 2019, 7:56am UTC](https://discuss.elastic.co/t/filebeat-syslog-with-wrong-timestamp/195454/4 "2019-08-17T07:56:09Z")

</div>

Hi admlko,  
Thank you for your response.  
I tried with the same method but it did not help to resolve my issue.  
I dont know what else could be missing from my setup.  
Do you need any configuration from me end for further checking?

---

<div class="post-metadata">

**Author:** ![Ryne\_Keel](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ryne_keel/32/42827_2.png) [@Ryne\_Keel](https://discuss.elastic.co/u/Ryne_Keel)\
**Post date:** [September 10, 2019, 9:28pm UTC](https://discuss.elastic.co/t/filebeat-syslog-with-wrong-timestamp/195454/5 "2019-09-10T21:28:40Z")

</div>

I am fairly certain that 7.3.1 broke var.convert\_timezone for the system module as I have it working in 7.2 but can't get it to work in 7.3.1.

It is likely a bug.

> <https://github.com/elastic/beats/issues/13489>

---

<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:** [October 8, 2019, 9:28pm UTC](https://discuss.elastic.co/t/filebeat-syslog-with-wrong-timestamp/195454/6 "2019-10-08T21:28:50Z")

</div>

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