Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Release 0.65.0 #677

Merged
merged 5 commits into from
Feb 20, 2025
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
31 changes: 31 additions & 0 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
@@ -1,5 +1,36 @@
# Changelog

## 0.65.0 2025-02-20

* Google Cloud SQL: Support IAM Authentication
- This allows monitoring of Google Cloud SQL databases using the existing
`db_use_iam_auth` / `DB_USE_IAM_AUTH` setting: If enabled, the collector
fetches a short-lived token for logging into the database instance from the
GCP API, instead of using a hardcoded password in the collector
configuration file
- To set this up, see our [updated Google Cloud SQL setup
documentation](https://pganalyze.com/docs/install/google_cloud_sql/01_create_monitoring_user)
* Start collecting and report pg_stat_statements_info stats
- This makes it easier to track down some pg_stat_statements-related
problems
* Support monitoring non-Heroku databases with Heroku-hosted collector
* Follow symlinks when tracking storage stats for data directory
- This fixes storage statistics accounting for data directories symlinked
to other partitions
* Fix pg_hint_plan handling for collector-driven Query Tuning workflow
* Fix errors when collecting stats about frequently-locked partitions
* Fix receiving logs through syslog
- This was inadvertently broken by the log parsing changes in v0.58.0
* Avoid log parsing error when database connection cannot be established
- This was only a secondary problem, but the stack trace in the logs could
make it harder to track down the root cause
* Sign built Go binaries for macOS
- Due to security enhancements in newer macOS versions, unsigned Go
binaries may hang when built and executed locally; signing makes it
easier to debug the collector on macOS
* Update Go version to 1.23
* Update Dockerfile alpine base image to 3.21

## 0.64.1 2025-01-08

* Fix database connection leak in buffercache logic
Expand Down
4 changes: 2 additions & 2 deletions contrib/helm/pganalyze-collector/Chart.yaml
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
apiVersion: v2
name: pganalyze-collector
version: 0.64.1
appVersion: "v0.64.1"
version: 0.65.0
appVersion: "v0.65.0"
type: application
description: pganalyze statistics collector
home: https://pganalyze.com/
Expand Down
2 changes: 1 addition & 1 deletion packages/Makefile
Original file line number Diff line number Diff line change
@@ -1,5 +1,5 @@
export NAME ?= pganalyze-collector
export VERSION ?= 0.64.1
export VERSION ?= 0.65.0
export GIT_VERSION ?= v$(VERSION)
#export GIT_VERSION=HEAD
#export GIT_VERSION=618e85ce5ed5365bc7d9d9da866fdeb73bac5a55
Expand Down
2 changes: 1 addition & 1 deletion util/version.go
Original file line number Diff line number Diff line change
@@ -1,4 +1,4 @@
package util

const CollectorVersion = "0.64.1"
const CollectorVersion = "0.65.0"
const CollectorNameAndVersion = "pganalyze-collector " + CollectorVersion
Loading