# Filebeat haproxy module timezone issue

**URL:** <https://discuss.elastic.co/t/filebeat-haproxy-module-timezone-issue/220144>\
**Category:** Beats\
**Tags:** filebeat\
**Created:** [February 20, 2020, 9:40am UTC](https://discuss.elastic.co/t/filebeat-haproxy-module-timezone-issue/220144 "2020-02-20T09:40:53Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Henrik\_Magnusson](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/henrik_magnusson/32/63007_2.png) [@Henrik\_Magnusson](https://discuss.elastic.co/u/Henrik_Magnusson)\
**Post date:** [February 20, 2020, 9:40am UTC](https://discuss.elastic.co/t/filebeat-haproxy-module-timezone-issue/220144/1 "2020-02-20T09:40:53Z")

</div>

Hi!

I have a problem when sending haproxy logs with the filebeat module for haproxy directly to elasticsearch.

The issue is that my systems are using timezone CET, so the logs are written into haproxy.log using my local timezone. In other words a log that is created at 0927CET will be written with the timestamp Feb 20 09:27:42.

When browsing with Kibana, the entry will be shown as 10:27:42. Kibana is using the webbrowser timezone, which is the same (CET).

The /etc/filebeat/modules.d/haproxy.yml looks like this

```
- module: haproxy
  log:
    enabled: true
    var.input: file

```

From other posts I have tried to add var.convert\_timezone: true, but it doesn't seem to have any effect.

After each change I have dropped the indexpattern and index in Kibana. I have deleted the ingest pipeline in Elasticsearch. But it doesn't seem to work anyway.

I am using ELK components with version 7.5.1.

Regards  
Henrik

---

<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:** [March 19, 2020, 9:40am UTC](https://discuss.elastic.co/t/filebeat-haproxy-module-timezone-issue/220144/2 "2020-03-19T09:40:54Z")

</div>

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