| From: | Durgamahesh Manne <maheshpostgres9(at)gmail(dot)com> |
|---|---|
| To: | David Steele <david(at)pgmasters(dot)net> |
| Cc: | Achilleas Mantzios <achill(at)matrix(dot)gatewaynet(dot)com>, "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org>, Andreas Kretschmer <andreas(at)a-kretschmer(dot)de>, Simon Riggs <simon(at)2ndquadrant(dot)com> |
| Subject: | Regarding pgaudit log_directory |
| Date: | 2019-03-31 19:01:56 |
| Message-ID: | CAJCZko+jkrziFxPKuOuoHU+LOBqH4fm96NYdFUtP=VQ6dE8LoQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Saturday, March 30, 2019, David Steele <david(at)pgmasters(dot)net> wrote:
> On 3/29/19 3:32 PM, Durgamahesh Manne wrote:
>
>>
>> I could not find parameter related to pgaudit log_directory .
>>
>
> pgAudit does not support logging outside the standard PostgreSQL logging
> facility and there are no plans for such a feature.
>
> The general solution is to use Splunk, ELK, etc. to do manipulation of the
> PostgreSQL logs.
>
> Regards,
> --
> -David
> david(at)pgmasters(dot)net
>
Hi
Please let me know open source application interface to do manipulation of
pgaudit logs only
As I have installed pgaudit successfully
Regards
Durgamahesh Manne
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Durgamahesh Manne | 2019-03-31 19:26:32 | Regarding pgaudit |
| Previous Message | Durgamahesh Manne | 2019-03-31 19:01:30 | Re: Regarding pgaudit log_directory |