# PostgreSQL Fleet integration

**URL:** https://discuss.elastic.co/t/postgresql-fleet-integration/364073
**Category:** Beats
**Tags:** fleet, filebeat
**Created:** [July 30, 2024, 3:39pm UTC](https://discuss.elastic.co/t/postgresql-fleet-integration/364073 "2024-07-30T15:39:26Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![yar](https://avatars.discourse-cdn.com/v4/letter/y/858c86/32.png) [@yar](https://discuss.elastic.co/u/yar)
#### Post date: [July 30, 2024, 3:39pm UTC](https://discuss.elastic.co/t/postgresql-fleet-integration/364073/1 "2024-07-30T15:39:26Z")

</div>

Hi!

I installed postgresql integration, added path to the csvlog, however, the logs are not parsed properly. Also I updated postgresql configuration in accordance with [this](https://www.elastic.co/docs/current/en/integrations/postgresql#log). The main problem is that postgresql query which should be in `postgresql.log.query` filed is in `message` field. In addition, I have 13 empty fields, however, I expect at least a few of them to have some data.  
 ![зображення](https://us1.discourse-cdn.com/elastic/original/3X/b/9/b9428909392dd03c65b351240fc8b2374df1c8ca.png)

---

<div class="post-metadata">

### Author: ![yar](https://avatars.discourse-cdn.com/v4/letter/y/858c86/32.png) [@yar](https://discuss.elastic.co/u/yar)
#### Post date: [August 1, 2024, 2:35pm UTC](https://discuss.elastic.co/t/postgresql-fleet-integration/364073/2 "2024-08-01T14:35:07Z")

</div>

The issue is caused by postgresql logging itself. When you get the csv schema of a log, and add raw csv log in some cases you'll be able to see the inconsistencies in how the table is formed.