# How to add the timezone information for Postgresql module in Filebeat?

**URL:** https://discuss.elastic.co/t/how-to-add-the-timezone-information-for-postgresql-module-in-filebeat/172244
**Category:** Beats
**Tags:** filebeat
**Created:** [March 14, 2019, 4:28am UTC](https://discuss.elastic.co/t/how-to-add-the-timezone-information-for-postgresql-module-in-filebeat/172244 "2019-03-14T04:28:52Z")
**Posts on this page:** 6
**Page:** 1

<div class="post-metadata">

### Author: ![Puneet\_Patwari](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/puneet_patwari/32/41215_2.png) [@Puneet\_Patwari](https://discuss.elastic.co/u/Puneet_Patwari)
#### Post date: [March 14, 2019, 4:28am UTC](https://discuss.elastic.co/t/how-to-add-the-timezone-information-for-postgresql-module-in-filebeat/172244/1 "2019-03-14T04:28:53Z")

</div>

I am using filebeat modules for syslog and postgresql. For System module, `var.convert_timezone` preserves the the timezone info in the ingest pipeline. However, this is not possible for `postgresql` module. I tried adding `add_locale` processor in the filebeat.yml but it does not work for the `postgresql` module. Please help me with this problem.

---

<div class="post-metadata">

### Author: ![steffens](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/steffens/32/79630_2.png) [@steffens](https://discuss.elastic.co/u/steffens)
#### Post date: [March 14, 2019, 2:18pm UTC](https://discuss.elastic.co/t/how-to-add-the-timezone-information-for-postgresql-module-in-filebeat/172244/2 "2019-03-14T14:18:13Z")

</div>

The `var.convert_timezone` setting does not directly convery the timestamp. It modifies the filebeat processor list and modifies the indest node pipeline. The `add_locale` processor does not convert the time, but it adds information about the machines location to the event. In ingest node the `date` processor is used for converting the timestamp.

You will have to adapt `postgresql/log/ingest/pipeline.json` as well. and run `filebeat setup --pipeline`, so to update Ingest Node.

---

<div class="post-metadata">

### Author: ![Puneet\_Patwari](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/puneet_patwari/32/41215_2.png) [@Puneet\_Patwari](https://discuss.elastic.co/u/Puneet_Patwari)
#### Post date: [March 15, 2019, 6:29am UTC](https://discuss.elastic.co/t/how-to-add-the-timezone-information-for-postgresql-module-in-filebeat/172244/3 "2019-03-15T06:29:13Z")

</div>

Hi @steffens, thanks for the response. I had to do adapt the `pipeline.json` for my usecase and it works perfectly. I hope that in future this property is added in the official repository of beats.

---

<div class="post-metadata">

### Author: ![steffens](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/steffens/32/79630_2.png) [@steffens](https://discuss.elastic.co/u/steffens)
#### Post date: [March 15, 2019, 2:53pm UTC](https://discuss.elastic.co/t/how-to-add-the-timezone-information-for-postgresql-module-in-filebeat/172244/4 "2019-03-15T14:53:06Z")

</div>

A pull request with your change or issue for enhancement request would be very welcome: [https://github.com/elastic/beats](https://github.com/elastic/beats) 😉

---

<div class="post-metadata">

### Author: ![Puneet\_Patwari](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/puneet_patwari/32/41215_2.png) [@Puneet\_Patwari](https://discuss.elastic.co/u/Puneet_Patwari)
#### Post date: [March 16, 2019, 12:24pm UTC](https://discuss.elastic.co/t/how-to-add-the-timezone-information-for-postgresql-module-in-filebeat/172244/5 "2019-03-16T12:24:09Z")

</div>

Okay @steffens, I will do that by Monday. Thanks. 😃

---

<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: [April 13, 2019, 12:24pm UTC](https://discuss.elastic.co/t/how-to-add-the-timezone-information-for-postgresql-module-in-filebeat/172244/6 "2019-04-13T12:24:10Z")

</div>

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