Hi @KimJisung - The best option here is to set up Audit Logging through the PostgreSQL (Single Server) extension pgAudit
and then have events forwarded to Azure Monitor for investigation, or dig through the resulting file looking for the truncating events. Please see: Audit logging in Azure Database for PostgreSQL - Single Server
Alerting will be helpful, as you can be notified and respond in a timely manner in terms of limiting the amount of audit log detail being captured. As for the alert not being triggered, what is the storage % or storage_used figure when the specific table is truncated...is that figure below 30%? Perhaps the trigger isn't firing because the rule is not specific to the condition needing to be triggered upon. The storage_used
and storage %
may not be calculated as expected. Please see the Azure Database for PostgreSQL Metrics and how to setup alerts.
Regards,
Mike