--- title: pgwatch v6: dashboards reimagined, and a reaper that... description: pgwatch v6.0.0-beta ships a full dashboard rebuild on Grafana's new v13 schema, giving Prometheus sources dashboard parity with Postgres, including a new... canonical: https://daily.dev/posts/pgwatch-v6-dashboards-reimagined-and-a-reaper-that-doesn-t-choke-hwpxiyino twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: pgwatch v6: dashboards reimagined, and a reaper that doesn't choke | daily.dev og:description: pgwatch v6.0.0-beta ships a full dashboard rebuild on Grafana's new v13 schema, giving Prometheus sources dashboard parity with Postgres, including a new... og:url: https://daily.dev/posts/pgwatch-v6-dashboards-reimagined-and-a-reaper-that-doesn-t-choke-hwpxiyino og:image: https://api.daily.dev/og/posts/hWPXiYinO.png og:image:alt: pgwatch v6: dashboards reimagined, and a reaper that doesn't choke og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # pgwatch v6: dashboards reimagined, and a reaper that doesn't choke **[CYBERTEC PostgreSQL](https://daily.dev/sources/cybertec_postgresql)** · 4 min read · 19 upvotes · 1 comments ## Summary pgwatch v6.0.0-beta ships a full dashboard rebuild on Grafana's new v13 schema, giving Prometheus sources dashboard parity with Postgres, including a new Patroni Cluster Overview dashboard. The release also hardens the reaper core after a real production incident where a 400-source fleet stopped collecting due to DNS/network brownouts: hung TCP/discovery calls now run under bounded timeouts, and failed discovery queries no longer tear down existing monitoring, instead falling back to the last known-good list. Additional fixes include a SourceReaper deadlock, graceful degradation on sink outages, sanitizing NaN/Inf values before they leak into stored measurements, and a broken v12 replication lag panel. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### What caused pgwatch to stop collecting metrics across an entire fleet of Postgres sources? A shared-infrastructure DNS/network brownout caused calls like Ping or discovery queries to hang on half-open TCP connections until the kernel timed them out, taking 15 to 30 minutes on Linux. Additionally, a failed discovery query used to tear down monitoring for every already-discovered database and rebuild it from scratch, worsening a fleet of roughly 400 sources that stopped collecting once or twice a month. _Teams debugging flaky monitoring fleets can follow fixes like this one on daily.dev._ ### What changed in pgwatch v6.0.0-beta for handling failed Postgres discovery queries? A failed discovery resolution with a non-empty cache now just logs a warning and keeps serving the last known-good list of databases, instead of tearing down monitoring for every already-discovered database. The teardown now only happens if there was never a successful resolution to fall back on, mirroring a cache pgwatch already used for Patroni cluster membership. _daily.dev helps engineers track reliability changes like this before upgrading monitoring tools._ ### Does pgwatch v6.0.0-beta support dashboards for Patroni clusters? Yes, pgwatch v6.0.0-beta adds a new Patroni Cluster Overview dashboard built on Grafana's v13 schema, fed by the patroni Prometheus preset. It includes per-cluster health summaries, node role and leader-lock panels, DCS-last-seen age, WAL write/received/replayed location, and panels for Clusters Without Leader and Paused Clusters to surface split-brain risk. _Ops teams evaluating Patroni observability options can track releases like this on daily.dev._ ## Community discussion Top comments from developers on daily.dev. **@agustinbarrientos** · 0 upvotes > I'd test the last-known-good cache with a DNS outage that overlaps a real source deletion. The reaper shouldn't resurrect the deleted source when discovery returns. A recovery case should also prove that the 32-worker queue drains without a reconnection burst. ## Similar posts on daily.dev - [pgwatch v6: Prometheus becomes a source, not just a sink](https://daily.dev/posts/pgwatch-v6-prometheus-becomes-a-source-not-just-a-sink-lkseom3c1) · CYBERTEC PostgreSQL · 5 upvotes · 0 comments - [pgwatch v4 is out\!](https://daily.dev/posts/pgwatch-v4-is-out--jrjzlkupd) · PostgreSQL · 0 upvotes · 0 comments - [pgwatch v4-beta is out\!](https://daily.dev/posts/pgwatch-v4-beta-is-out--gp9nj8rul) · CYBERTEC PostgreSQL · 1 upvotes · 0 comments --- Tags: [#postgresql](https://daily.dev/tags/postgresql), [#observability](https://daily.dev/tags/observability), [#grafana](https://daily.dev/tags/grafana), [#prometheus](https://daily.dev/tags/prometheus) [View this post on daily.dev](https://daily.dev/posts/pgwatch-v6-dashboards-reimagined-and-a-reaper-that-doesn-t-choke-hwpxiyino) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"pgwatch v6: dashboards reimagined, and a reaper that doesn't choke","url":"https://daily.dev/posts/pgwatch-v6-dashboards-reimagined-and-a-reaper-that-doesn-t-choke-hwpxiyino","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/pgwatch-v6-dashboards-reimagined-and-a-reaper-that-doesn-t-choke-hwpxiyino"},"datePublished":"2026-08-31T08:19:39.040Z","dateModified":"2026-08-31T08:20:01.968Z","description":"pgwatch v6.0.0-beta ships a full dashboard rebuild on Grafana's new v13 schema, giving Prometheus sources dashboard parity with Postgres, including a new...","image":"https://media.daily.dev/image/upload/s--foaA6JGU--/f_auto/v1722860399/public/Placeholder%2004","thumbnailUrl":"https://media.daily.dev/image/upload/s--foaA6JGU--/f_auto/v1722860399/public/Placeholder%2004","isAccessibleForFree":true,"articleSection":"CYBERTEC PostgreSQL","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"CYBERTEC PostgreSQL","logo":"https://media.daily.dev/image/upload/s--T-0b7qSy--/f_auto/v1720886268/logos/cybertec_postgresql","url":"https://daily.dev/sources/cybertec_postgresql"},"commentCount":1,"discussionUrl":"https://daily.dev/posts/pgwatch-v6-dashboards-reimagined-and-a-reaper-that-doesn-t-choke-hwpxiyino","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":19},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":1}],"keywords":"postgresql,observability,grafana,prometheus","timeRequired":"PT4M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"CYBERTEC PostgreSQL","item":"https://daily.dev/sources/cybertec_postgresql"},{"@type":"ListItem","position":3,"name":"pgwatch v6: dashboards reimagined, and a reaper that doesn't choke"}]} {"@context":"https://schema.org","@type":"WebPage","@id":"https://daily.dev/posts/pgwatch-v6-dashboards-reimagined-and-a-reaper-that-doesn-t-choke-hwpxiyino","comment":[{"@type":"Comment","text":"I’d test the last-known-good cache with a DNS outage that overlaps a real source deletion. The reaper shouldn’t resurrect the deleted source when discovery returns. A recovery case should also prove that the 32-worker queue drains without a reconnection burst.","datePublished":"2026-09-02T02:31:51.569Z","url":"https://daily.dev/posts/hWPXiYinO#c-T8MFKV6eN","author":{"@type":"Person","name":"Agustin Barrientos","url":"https://daily.dev/agustinbarrientos","image":"https://media.daily.dev/image/upload/s--5ayxQnqn--/f_auto/v1788281802/avatars/avatar_wQYYVe5Tbj0NJ7C7qPoa8?_a=BAMAMicg0"}}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/pgwatch-v6-dashboards-reimagined-and-a-reaper-that-doesn-t-choke-hwpxiyino#faq","mainEntity":[{"@type":"Question","name":"What caused pgwatch to stop collecting metrics across an entire fleet of Postgres sources?","acceptedAnswer":{"@type":"Answer","text":"A shared-infrastructure DNS/network brownout caused calls like Ping or discovery queries to hang on half-open TCP connections until the kernel timed them out, taking 15 to 30 minutes on Linux. Additionally, a failed discovery query used to tear down monitoring for every already-discovered database and rebuild it from scratch, worsening a fleet of roughly 400 sources that stopped collecting once or twice a month. Teams debugging flaky monitoring fleets can follow fixes like this one on daily.dev."}},{"@type":"Question","name":"What changed in pgwatch v6.0.0-beta for handling failed Postgres discovery queries?","acceptedAnswer":{"@type":"Answer","text":"A failed discovery resolution with a non-empty cache now just logs a warning and keeps serving the last known-good list of databases, instead of tearing down monitoring for every already-discovered database. The teardown now only happens if there was never a successful resolution to fall back on, mirroring a cache pgwatch already used for Patroni cluster membership. daily.dev helps engineers track reliability changes like this before upgrading monitoring tools."}},{"@type":"Question","name":"Does pgwatch v6.0.0-beta support dashboards for Patroni clusters?","acceptedAnswer":{"@type":"Answer","text":"Yes, pgwatch v6.0.0-beta adds a new Patroni Cluster Overview dashboard built on Grafana's v13 schema, fed by the patroni Prometheus preset. It includes per-cluster health summaries, node role and leader-lock panels, DCS-last-seen age, WAL write/received/replayed location, and panels for Clusters Without Leader and Paused Clusters to surface split-brain risk. Ops teams evaluating Patroni observability options can track releases like this on daily.dev."}}]} ```