Skip to content

Releases: pganalyze/collector

v0.14.0

16 Jul 04:04
Compare
Choose a tag to compare
  • Introduce once-per-minute query statistics collection
    • Enabled for PostgreSQL 9.4+
    • This replaces the old logic for query stats without text (statement_text_frequency),
      and is always active
    • Statistics data gets sent with every full snapshot
  • Backend counts: Support retrieving stats for Postgres 9.5 and older
  • Log Insights: Add support for detecting aggressive vacuums (Postgres 11+)
  • Parse serialization failure log events (U138 and U139)
  • Have systemd restart the collector after crashes Dom Hutton #23

v0.13.1

18 Jun 09:13
Compare
Choose a tag to compare
  • Don't error out on pg_stat_replication.replay_lsn being NULL #21

v0.13.0

15 Jun 17:36
Compare
Choose a tag to compare
  • Support basic vacuum information for Postgres 9.5 and older
  • Track connection counts per database and per role
  • Add ignore_table_pattern / IGNORE_TABLE_PATTERN option
  • Avoid errors when collecting from AWS Aurora for Postgres instances
  • Log Insights improvements
    • Better setup help
    • Increase read rate for RDS log downloader from 100 to 1000 lines
    • Add support for extracting EXPLAIN plans from auto_explain output
    • Fix autovacuum, autoanalyze and checkpoint completed parsing for PG 10
    • Avoid sending unparsed explain text for truncated log lines
    • Detect vacuum/analyze skipped log lines

v0.12.0

05 Mar 09:34
Compare
Choose a tag to compare
  • Set username/database name correct for Heroku logstreams
  • Support additional ryslog format that contains user/db/app information
  • Update to Go 1.10

v0.11.0

02 Feb 11:29
Compare
Choose a tag to compare
  • Add support for Log Insights on self-hosted systems
  • Add additional log classifications, speed up analysis by reusing regexps
  • Add "--analyze-logfile" option to test collector with local logfiles
  • Associate truncated queries to the correct error fingerprint
  • Update to Go 1.9.3

v0.10.0

02 Nov 20:48
Compare
Choose a tag to compare
  • Update pg_query_go to Postgres 10 and fingerprint version 2
    • This is a breaking change in collector output, as queries will now
      be fingerprinted differently
  • Activity snapshots
    • Use pg_stat_activity helper when it exists
    • Track VACUUM progress in activity snapshots
    • Activity data: Ignore backends that are not visible to the user
    • Allow additional digits for PID in pg_stat_activity Joseph Bylund
  • Don't collect backend data for full snapshot anymore, this is all delegated
    to activity snapshots now
  • Update to Go 1.9.2
  • RDS pgss check: Add additional safety against nil pointer dereferences

v0.9.17

31 Oct 21:12
Compare
Choose a tag to compare
  • Logs: Fix regexp for 9.5 vacuum output (skip pins, but not skip frozen)
  • Update to Go 1.9.1 release
  • Allow disabling collection of relation/schema information
  • Add experimental activity snapshots
    • This is not for public consumption yet, and trying to use it will result in
      an error from the server - but watch this space :)

v0.9.16

06 Oct 07:30
Compare
Choose a tag to compare
Release 0.9.16

v0.9.15

02 Oct 11:23
Compare
Choose a tag to compare
  • Update pg_query_go / libpg_query to 9.5-1.6.2
    • Updates the query fingerprinting logic to avoid seeing different
      FETCH/DECLARE/CLOSE cursor names as unique queries - statistics on this
      are not going to be useful in most cases, and will clog the processing
      pipeline
    • Updates the query fingerprinting logic to ignore the table name for
      CREATE TEMPORARY TABLE
    • Updates the query fingerprinting logic to better handle the values list
      for INSERT statements to group complex, but similar statements together
  • Support specifying db_sslmode=verify-full and passing certificate information
    using db_sslrootcert / db_sslrootcert_contents
    • The collector packages now also ship a set of known DB-as-a-Service CA
      certificates, starting with the often needed rds-ca-2015-root certificate
      (just pass that term instead of a path to db_sslrootcert)
  • Support for Postgres 10
  • Heroku: Support specifying configuration name in log drain endpoints
  • RDS: Ensure to delete temporary log files quickly after they are submitted

v0.9.14

06 Jun 10:55
Compare
Choose a tag to compare
  • Add support for Heroku logdrains