Skip to content

Releases: pganalyze/collector

v0.9.3

08 Aug 03:29
Compare
Choose a tag to compare
  • Correctly identify PostgreSQL data directory and pg_xlog location
  • Avoid potential NaN values in disk stats for self-hosted systems
  • Don't write state file for dry runs by default

v0.9.2

01 Aug 09:30
Compare
Choose a tag to compare
  • PostgreSQL 9.2, 9.3 and 9.6 Support
  • Adjust default config and state file path to match packages
  • Allow using postgres driver default values for connection credentials

v0.9.1

28 Jul 11:15
Compare
Choose a tag to compare
  • Add support for logging to syslog instead of stderr
  • Init scripts for systemd, upstart and sysvinit (see contrib/ directory)
  • Packaging scripts for common Linux distributions (see packages/ directory)

v0.9.0

18 Jul 04:17
Compare
Choose a tag to compare
  • First official release of new protocol buffers-based collector

v0.9.0rc8

08 Jul 09:08
Compare
Choose a tag to compare
v0.9.0rc8 Pre-release
Pre-release
  • Significant restructuring of the codebase
    • We're now sending data using the protocol buffers format
    • Snapshot data is directly uploaded to S3
  • Query, table and system statistics are diff-ed on the client side
  • Support for monitoring system metrics on self-hosted systems is added again
  • New safety mechanisms against stuck/slow collector runs

v0.9.0rc7

14 Apr 11:46
Compare
Choose a tag to compare
v0.9.0rc7 Pre-release
Pre-release
  • Add support for RDS enhanced monitoring
  • Simplify dependencies and document OSS licenses in use

v0.9.0rc6

08 Apr 06:57
Compare
Choose a tag to compare
v0.9.0rc6 Pre-release
Pre-release
  • Bugfixes for AWS Instance Role handling

v0.9.0rc5

08 Apr 06:03
Compare
Choose a tag to compare
v0.9.0rc5 Pre-release
Pre-release
  • Introduce new --diff-statements option (default off for now)
    • This calculates the diff for the counter values of pg_stat_statements on the client (i.e. collector),
      instead of the server for increased accuracy and protection against out-of-order processing
  • Introduce "opts" to the snapshot, for indicating which options were chosen
  • Never open more than 1 connection to the same database
    • This covers edge cases like sending a lot of SIGHUP signals
    • In case we detect more than 1 connection we error out and exit, to avoid
      clogging the database
  • Use AWS EC2 instance role if no credentials are specified

v0.9.0rc4

03 Apr 23:21
Compare
Choose a tag to compare
v0.9.0rc4 Pre-release
Pre-release
  • Ensure pg_toast schema is excluded when calculating index bloat

v0.9.0rc3

28 Mar 16:08
Compare
Choose a tag to compare
v0.9.0rc3 Pre-release
Pre-release
  • Send Postgres version to the server as well