From: | vijay patil <vijay(dot)postgres(at)gmail(dot)com> |
---|---|
To: | KENAN ÇİFTÇİ <kciftci89(at)gmail(dot)com> |
Cc: | pgsql-general(at)lists(dot)postgresql(dot)org |
Subject: | Re: Best Tool for PostgreSQL Auditing and Storing Audit Logs Separately |
Date: | 2025-04-16 05:15:24 |
Message-ID: | CAD5k+7zAUf827FLUnoYYFdd0YoD1Vmqz-QfmTMT5dgQu8KNKoQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Hi Kenan,
Thanks for the quick response.
Thanks
Vijay
On Tue, Apr 15, 2025 at 4:44 PM KENAN ÇİFTÇİ <kciftci89(at)gmail(dot)com> wrote:
> Hi,
>
> You can use pgaudit and pgauditlogtofile extension (
> https://github.com/fmbiete/pgauditlogtofile) together to write audit logs
> in a separate file.
>
> yours,
>
> Kenan Çiftçi
>
> On Tue, Apr 15, 2025 at 1:44 PM vijay patil <vijay(dot)postgres(at)gmail(dot)com>
> wrote:
>
>> Hi All,
>>
>> We are exploring auditing solutions for our PostgreSQL database and are
>> considering using pgaudit for this purpose. However, we have a few
>> questions:
>>
>> 1.
>>
>> *What is the best tool for auditing PostgreSQL databases?*
>> -
>>
>> We are specifically looking for a solution that offers detailed
>> auditing capabilities and is compatible with our setup.
>> 2.
>>
>> *Can we store the audit information separately from PostgreSQL logs
>> if we decide to use pgaudit?*
>> -
>>
>> We would prefer to keep the audit logs in a separate file or
>> location for easier management and analysis.
>>
>>
>> We appreciate any help or suggestions!
>>
>>
>> Thanks
>>
>> Vijay
>>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Laurenz Albe | 2025-04-16 07:31:46 | Re: Fwd: Identify system databases |
Previous Message | David G. Johnston | 2025-04-16 00:33:51 | Re: Fwd: Identify system databases |