Keith Fiske
Keith Fiske
This will require monitoring postgres logs since that is the only place that a reload is noted. May possibly be able to do this with Loki - https://github.com/CrunchyData/pgmonitor/issues/153
Examine if Loki can work as a log monitoring solution https://github.com/grafana/loki Example of using Grafana Explore with loki to make searching logs easier - https://grafana.com/blog/2020/04/08/loki-quick-tip-how-to-create-a-grafana-dashboard-for-searching-logs-using-loki-and-prometheus/ Another blog post to review...
This isn't an issue with the bloat calculation itself, but with the evaluation of the thresholds ``` POSTGRES_BLOAT WARNING: DB "mydb" (host:my.db.server) (db mydb) table public.instance rows:195969008 pages:13835076 shouldbe:13525027 (1.0X)...
# Description Add support for PG15. Not including pg_stat_statements_full query at this time. Disable JIT for the monitoring user to avoid suspected memory leak issue found with backrest query Fixes...
# Description Update the sysconfig file for Prometheus to use non-deprecated value for tsdb storage. Change to clearer `7d` value for retention. Reviewed other options in use by default for...
Noticed this in logs for prometheus ``` Sep 23 08:13:06 ha-test-kf-r7 prometheus: ts=2022-09-23T12:13:06.021Z caller=main.go:484 level=warn deprecation_notice="'storage.tsdb.retention' flag is deprecated use 'storage.tsdb.retention.time' instead." ``` Update the supplied sysconfig file to the...
PROCEDURES in PG11+ should may allow this to be a built in extension instead of an external script. Can also use similar scheduler that pg_partman is using to not require...
Creating an issue to document some discussions I've had about improving index check speed by using pgstatindex(). empty_pages/deleted_pages account for entire pages that are "bloat" avg_leaf_density provides a % free...