The Long Running Queries alert notifies you when its configured condition is met on PostgreSQL instances so you can investigate and respond.
Mini DBA describes this alert as: Active processes that have been running the same sql batch for a long period of time Huge queries may be consuming way too much of the servers resources The MaxThreshold represents number of minutes the batch must run to trigger the alert 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 concurrency pressure. Blocking, long sessions, and lock waits can turn a healthy server into a slow user experience, so the alert gives administrators an early route to the sessions, statements, and applications involved.
Enable it on any monitored PostgreSQL instance where this condition would require an administrator to investigate or communicate with the application team. Tune noisy development systems after you have a short baseline.
Threshold meaning: Queries. Major threshold: 1 minutes. Minor threshold: 0 minutes. 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.
Open the activity, blocking, and query views to identify the lead blocker, SQL text, wait type, login, host, and application. Prefer fixing the query or transaction pattern, but kill or cancel the blocking session when the business impact is higher than the rollback risk.
If this alert is noisy, check whether the workload naturally has short bursts. Raise the duration or threshold for expected batch windows, but keep a lower route for production systems where user-facing latency matters. Avoid simply disabling the alert until you know whether the noise is caused by threshold choice or by a real capacity trend.