Handle Azure PostgreSQL Auditing With Ease
summary
Shows how to enable pgaudit on Azure Database for PostgreSQL by checking shared_preload_libraries, restarting the server, and running CREATE EXTENSION per database, then choosing pgaudit.log options (recommend DDL and ROLE only). Explains changing log_line_prefix to capture user info, the PostgreSQL log limits (hourly files, default 3 days, 1 GB cap for READ/WRITE), and why sending logs to Azure Monitor into a central Log Analytics workspace with Kusto queries and a Logic App daily CSV email is preferable.
AI-written summary · about
chapters (6)
- 0:00Introduction
- 0:36What is auditing
- 2:20Azure PostgreSQL auditing
- 8:11Azure Monitor
- 11:35Demo: Azure PostgreSQL auditing
- 19:56Reporting on auditing data
related talks
27mAzure Database for PostgreSQL: 15 Essential Standards for Compliance and Security
29mFortifying Azure Database for PostgreSQL: Stop Intrusions in Their Tracks
27mAzure AD authentication with PostgreSQL Flexible Servers
40mPoastgreSQL Auditing, Authentication, and Security
47mWhat does it take to onboard an extension?
50mPostgreSQL Security. How Do We Think?
07mAll about Postgres security
47mUntangling the Web of PostgreSQL Permissions