collector
collector copied to clipboard
pganalyze statistics collector for gathering PostgreSQL metrics and log data
Hi, We are currently using the scaled version of pganalyze.I've set up the pganalyze collector using a Docker file and created a deployment, but I'm encountering issues accessing the logs...
5 attempts is probably too much, especially when each can take 30 seconds (or is it 120 seconds from `Timeout`?). This might explain why we've seen the collector take so...
https://www.postgresql.org/docs/current/monitoring-stats.html#MONITORING-PG-STAT-IO-VIEW Todo: - [ ] refactor to use enums instead of strings for the classification columns - [ ] handle `stats_reset` properly - [ ] rename `runner/queries.go`, maybe to `runner/full_1min.go`?
Companion PR to https://github.com/pganalyze/pganalyze-docs/pull/257
I am looking to set up pganalyze on my Nix-based system. Unfortunately, due to the way I am handling secrets, I cannot directly provide the password in an environment variable...
Leaving this as draft for now until https://github.com/pganalyze/collector/pull/526 is merged (which defines PostgresVersion17), and to give the [upstream work](https://git.postgresql.org/gitweb/?p=postgresql.git;a=commit;h=667e65aac354975c6f8090c6146fceb8d7b762d6) a bit longer to settle.
Followup to #610, this makes it so we only fall back to querying `pg_stats` directly on Postgres 17 and older, since the old function definition will still work until the...
#605 succeeded in reducing memory usage, but it also caused collector query time in pg_stat_statements to increase. This PR tries to solve both issues by writing query texts to a...
This is intended to help identify servers that belong together, to allow the pganalyze app to group them in an overview, offer data in combined views, or allow Index Advisor...