chore(deps): update dependency prometheus-community/postgres_exporter (v0.19.1 → v0.20.1) #66
Loading…
Reference in a new issue
No description provided.
Delete branch "renovate/postgres_exporter-and-its-dashboard"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This PR contains the following updates:
v0.19.1→v0.20.1Merging deploys nothing.
scripts/generate-grafana-dashboards.shpins a version that takes effect only when that script runs. Run it against the cluster after merging.Release Notes
prometheus-community/postgres_exporter (prometheus-community/postgres_exporter)
v0.20.1: 0.20.1 / 2026-07-07Compare Source
pg_replication_slotsby @megative in #1313v0.20.0: 0.20.0 / 2026-06-29Compare Source
BREAKING CHANGES:
Collector flag changes
The
replication_slotcollector has been renamed toreplication_slots.Users explicitly enabling or disabling this collector must update their flags:
--collector.replication_slot->--collector.replication_slots--no-collector.replication_slot->--no-collector.replication_slotsThe
--disable-settings-metricsflag andPG_EXPORTER_DISABLE_SETTINGS_METRICSenvironment variable have been removed.Use
--no-collector.settingsinstead.Metric name changes
The metrics previously exposed by the
replication_slotcollector have beenrenamed to use the
pg_replication_slots_prefix. Update alerts, recordingrules, and dashboards that reference these metrics:
pg_replication_slot_slot_current_wal_lsn->pg_replication_slots_slot_current_wal_lsnpg_replication_slot_slot_confirmed_flush_lsn->pg_replication_slots_slot_confirmed_flush_lsnpg_replication_slot_slot_is_active->pg_replication_slots_slot_is_activepg_replication_slot_safe_wal_size_bytes->pg_replication_slots_safe_wal_size_bytespg_replication_slot_wal_status->pg_replication_slots_wal_statusStandalone collector behavior
The
settings,stat_activity,stat_archiver,stat_replication, andreplication_slotsmetrics now come from standalone collectors instead of thelegacy default metric map.
These metrics no longer honor
--metric-prefix, no longer include deprecatedconstantLabels, and are no longer disabled by--disable-default-metrics.To stop collecting them, disable the corresponding collector explicitly with
its
--no-collector.*flag.pg_settingsmetrics to the standalonesettingscollector by @ArthurSens in #1303stat_archivermetrics to a standalone collector by @ArthurSens in #1304stat_activitymetrics to a standalone collector by @ArthurSens in #1305stat_replicationmetrics to a standalone collector by @ArthurSens in #1306replication_slottoreplication_slotsand move replication slot metrics to a standalone collector by @ArthurSens in #1307pg_stat_progress_vacuummetrics for cross-database vacuums by @steinbrueckri in #1262pg_settingscollection whenshort_descis NULL by @jun-gradial in #1327Configuration
📅 Schedule: (in timezone Europe/Helsinki)
* 0-4,22-23 * * 1-5)* * * * 0,6)* 17-20 * * 1-5)* 10-19 * * 0,6)🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate CLI.
ec99ee4c31613cf731d0View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.