# \[Filebeat\] Postgres module

**URL:** <https://discuss.elastic.co/t/filebeat-postgres-module/173283>\
**Category:** Discussions en français\
**Created:** [March 21, 2019, 10:06am UTC](https://discuss.elastic.co/t/filebeat-postgres-module/173283 "2019-03-21T10:06:18Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![gabriel\_tessier](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/gabriel_tessier/32/27911_2.png) [@gabriel\_tessier](https://discuss.elastic.co/u/gabriel_tessier)\
**Post date:** [March 25, 2019, 8:03am UTC](https://discuss.elastic.co/t/filebeat-postgres-module/173283/2 "2019-03-25T08:03:31Z")

</div>

Bonjour,

Juste au cas ou si t'as pas déjà trouvé une solution, y'a un cas qui semble similaire ici avec une date mal formatée :

> [@Postgres logs not properly parsed by filebeat](https://discuss.elastic.co/t/postgres-logs-not-properly-parsed-by-filebeat/137371):
>
> Hi, I have started with Elastic Stack recently. My use case is to monitor multiple raspberry pis with Beats module and visualize the data in Kibana Dashboards. I tried to set up Metricbeat and filebeat on Raspi 3, it was built and was running successfully. Now when I enabled the Postgres module, the data is still sent to elasticsearch but with the error message. Separate fields which are mentioned [here](https://www.elastic.co/guide/en/beats/filebeat/master/exported-fields-postgresql.html) Here is the single packet { "\_index": "filebeat-6.2.4-2018.06.25", "\_type": "doc", "\_…

---

_[View the full topic](https://discuss.elastic.co/t/filebeat-postgres-module/173283)._