The Missing Analyze History alert notifies you when its configured condition is met on PostgreSQL instances so you can investigate and respond.
Mini DBA describes this alert as: Large user tables with no recorded manual analyze or autoanalyze history. Missing statistics can cause poor row estimates and bad query plans. Mini DBA evaluates this alert once a minute so changes are detected quickly. Because duration is used, Mini DBA can avoid treating a single short spike as a full incident when the condition clears quickly.
This alert highlights PostgreSQL maintenance pressure. It helps identify tables or transaction patterns that can increase bloat, weaken planner statistics, or allow transaction ID age to approach an unsafe level.
Enable it on PostgreSQL systems where delayed maintenance, table bloat, stale statistics, or transaction ID age would require investigation. Use table and workload baselines to avoid treating short maintenance bursts as incidents.
Threshold meaning: Tables. Major threshold: 10 tables. Minor threshold: 0 tables. Comparison direction: over. Duration is used, so prefer requiring the condition to persist before paging people for transient spikes. For an over-threshold alert, decreasing a threshold makes that severity fire sooner; increasing it tolerates more load or pressure. Set the minor threshold as an early-warning level and the major threshold at the highest acceptable value for the service.
Review the affected tables, autovacuum and analyze history, dead tuples, transaction age, and long-running transactions. Tune table-level maintenance settings or run controlled maintenance, then confirm that cleanup and statistics collection keep pace with the workload.
Use duration and table-count thresholds to avoid paging on a short maintenance cycle. Keep the alert sensitive enough to catch tables that remain overdue, transaction age that keeps rising, or maintenance that repeatedly fails to catch up.