Re: Another way to do audit in DML operations in PostgreSQL >= 14
| От | Ron Johnson |
|---|---|
| Тема | Re: Another way to do audit in DML operations in PostgreSQL >= 14 |
| Дата | |
| Msg-id | CANzqJaD8ZTE4-n=VMR+rpuPgfzNx2VOX2VDNgkMGp8pLnRAinw@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: Another way to do audit in DML operations in PostgreSQL >= 14 (Bruce Momjian <bruce@momjian.us>) |
| Ответы |
Re: Another way to do audit in DML operations in PostgreSQL >= 14
|
| Список | pgsql-admin |
On Fri, Feb 23, 2024 at 9:29 AM Bruce Momjian <bruce@momjian.us> wrote:
On Thu, Feb 22, 2024 at 08:54:52PM -0800, S Hoffman wrote:
> Hi Lucio Chiessi,
>
> Dealing with large volumes of data can be a challenging task. If you struggle
> with this issue, one possible solution is to consider using external logging
> services. Specifically, asynchronous logging services or external logging
> services that are designed to handle streaming data may be effective options to
> explore. Some popular external logging services in this regard include
> Elasticsearch and Spunk, known for their ability to handle large volumes of
> data. If you have any questions or want to explore other options, please let me
> know.
Would remote syslog be an option too?
rsyslog feeding Qradar is great, but a DBA still needs his own logs. If there's a way to spit only pgaudit logs to rsyslog, and leave everything else go to stderr, I'd be a very happy camper.
В списке pgsql-admin по дате отправления: