All issues

Search results

A collector definition cannot contribute to collection_log.error_message, so a collector that knows why it returned nothing has nowhere to record it

Status: Open.

#3161 In erikdarlingdata/PerformanceMonitor;

· erikdarlingdata opened on Sep 7, 2026

The zero-output finding explains a quiet collector as an event collector at rest, and query_store is not one — the same sentence would reassure over a broken collector

Status: Open.

#3160 In erikdarlingdata/PerformanceMonitor;

· erikdarlingdata opened on Sep 7, 2026

pg_index_bloat and pg_index_usage_stats report index censuses differing by 65% for the same target, and neither doc names the other's population

Status: Open.

#3158 In erikdarlingdata/PerformanceMonitor;

· erikdarlingdata opened on Sep 7, 2026

pg_index_bloat measures one index per cycle: the work budget equals the measurement ceiling, so the largest candidate consumes the whole cycle — 1 of 2,457 candidates measured on the first successful run, and 43 can never be measured

Status: Open.

#3153 In erikdarlingdata/PerformanceMonitor;

· erikdarlingdata opened on Sep 7, 2026

27 of 43 servers fell 7 minutes behind for one hour: query_store's target reads slowed 9.8x fleet-wide while plan_correction, same shape and same run drop, stayed flat

Status: Open.

#3112 In erikdarlingdata/PerformanceMonitor;

· erikdarlingdata opened on Sep 7, 2026

Collector store writes fail in a pattern that correlates with continuous-aggregate refresh windows, and a failed write silently costs one sample on collectors with no watermark

Status: Open.

#3099 In erikdarlingdata/PerformanceMonitor;

· erikdarlingdata opened on Sep 6, 2026

[FEATURE] Auto force plan bot — detect bad Query Store plans (CPU-weighted), force with self-review, evict-first option

Status: Open.

#2138 In erikdarlingdata/PerformanceMonitor;

· erikdarlingdata opened on Aug 9, 2026