@checkstack/healthcheck-postgres-backend 0.3.5 → 0.4.1

package/CHANGELOG.md

@@ -1,5 +1,122 @@
 # @checkstack/healthcheck-postgres-backend
 
+## 0.4.1
+
+### Patch Changes
+
+- c55d7c6: Unify the healthcheck chart system on the `@checkstack/ui` SVG kit and
+  redesign the HealthCheck drawer.
+
+  - `@checkstack/ui` gains six chart primitives (each with a Storybook story):
+    `StackedTimeline` (stacked status counts per bucket on the colorblind-safe
+    status triad), `ChartTooltip` + `useBandHover` (the one shared chart
+    tooltip and its cursor hit-testing), `ChartCard` / `chartCardChromeClass`
+    (the premium gradient card chrome, flat on low-power devices), `StatTile`
+    (number-led metric tile with delta chip, sparkline/ribbon footer, and
+    click-to-expand disclosure), `DistributionBar` (stacked horizontal
+    distribution + legend, replaces pies), and `CategoryRibbon` (categorical
+    history ribbon). `TimeSeriesChart` gains a hover tooltip with a crosshair
+    marker.
+  - `@checkstack/common` adds four optional chart metadata keys to
+    `BaseHealthResultMeta`: `x-chart-priority` (tile sort weight, lower first,
+    default 100), `x-chart-good-direction` (`"up" | "down"`, which direction
+    of change is an improvement; consumers fall back to
+    `x-anomaly-direction`), and `x-chart-true-label` / `x-chart-false-label`
+    (prose for a boolean field's values wherever they surface in text, e.g. a
+    dominance chip reading "Usually successful (98%)" instead of "Usually
+    true"). Built-in collector backends annotate their headline metrics and
+    boolean fields accordingly (purely additive metadata).
+  - `@checkstack/healthcheck-frontend` rebuilds the drawer: a hero status
+    banner (status pill, healthy %, avg latency, interval, last run with the
+    exact datetime on hover, full-width status ribbon) replaces the metric
+    tiles; the status timeline and latency heroes share the `ChartCard`
+    chrome; the auto-generated charts become a prioritized, click-to-expand
+    2-up tile grid (collector ids demoted to hover titles); the anomaly
+    Expected/Trend derivation is consolidated into one tested module shared by
+    the latency hero and the tiles.
+
+  BREAKING CHANGES: `recharts` is removed from `@checkstack/healthcheck-frontend`
+  (and the unused dependency from `@checkstack/ui`); the
+  `HealthCheckStatusTimeline` and `SparklineTooltip` components are deleted.
+  Extensions rendering into `HealthCheckDiagramSlot` should build on the
+  `@checkstack/ui` chart primitives instead.
+
+- Updated dependencies [c55d7c6]
+- Updated dependencies [c55d7c6]
+  - @checkstack/healthcheck-common@1.13.0
+  - @checkstack/common@0.21.0
+  - @checkstack/backend-api@0.29.1
+
+## 0.4.0
+
+### Minor Changes
+
+- faf98f5: Security: config secrets (health-check strategy/collector credentials such as
+  SSH passwords, DB credentials, HTTP auth, and integration connection
+  credentials) ride ONE shared, domain-agnostic extraction channel instead of
+  being stored as plaintext or re-implemented per plugin.
+
+  New primitive and shared service:
+
+  - `configSecret({ id })` (in `@checkstack/backend-api`) declares an
+    extraction-channel secret keyed by a STABLE `id`, independent of field name or
+    position, so renaming or reordering a field never orphans its value. Use it
+    (not `configString({ "x-secret": true })`) for any credential whose config is
+    relayed to a satellite, projected to AI, or diffed by GitOps. `validateSecretIds`
+    rejects, at plugin registration, an `x-secret` field with no `id`, a duplicate
+    `id`, or a secret nested in an un-keyable container (array / record / tuple /
+    map) - so a mis-keyable schema fails boot rather than at run time.
+  - `ConfigSecretChannel` (in `@checkstack/secrets-backend`) is the single
+    extract / inflate / collect / redact / merge / delete / prune implementation.
+    Health-checks and integration connections both BIND it to their own scope
+    (marker prefix + internal-secret key layout); neither re-implements the walk.
+
+  Lifecycle (both bindings):
+
+  - **Write**: an inline value is extracted into the encrypted internal secret
+    store; the stored config keeps only an opaque marker. `${{ secrets.NAME }}`
+    references are stored verbatim and resolve through the active backend (local
+    or Vault) at run time.
+  - **Read**: configuration and connection reads strip `x-secret` values and
+    internal markers while keeping `${{ secrets.NAME }}` references visible; the
+    AI `getConfigurations` tool and create/update responses are redacted too. A
+    value never reaches a browser or an AI model context.
+  - **Run**: the core executor inflates markers/references in memory just before
+    the client is built. Satellites receive markers only and fetch values
+    just-in-time over the authenticated WS channel, per run, never persisted, then
+    fail CLOSED if any marker/reference survives resolution.
+  - **No orphan**: clearing a secret, removing a field/collector, swapping an
+    inline value for a reference, updating a connection, or deleting a
+    configuration/connection deletes the now-unreferenced internal secret. Cleanup
+    is schema-free (scans markers by prefix) and best-effort on delete, so it works
+    even when the owning plugin is uninstalled and never blocks a delete.
+  - **Forged-marker safe**: extract/inflate key each internal secret by the
+    SCHEMA leaf's stable `id`, never by an id parsed out of a stored marker string,
+    so a crafted marker can never resolve or delete another scope's secret.
+
+  Health-checks additionally get an idempotent, advisory-locked backfill that
+  moves pre-existing plaintext values into the internal store, and per-config-id
+  locking so concurrent writers across pods can never leave a dangling marker.
+  Integration connection credentials keep their released `__connref__:` marker
+  prefix and key layout (id equals the flat field name), so existing stored
+  connections are byte-compatible.
+
+  BREAKING CHANGES:
+
+  - Configuration and connection reads no longer include `x-secret` field values
+    (clients must treat blank-on-save as keep-existing; the bundled editors
+    already do).
+  - Satellites must be upgraded together with the core: an old satellite cannot
+    resolve the markers a new core stores, so its credentialed checks fail until
+    upgraded.
+
+### Patch Changes
+
+- Updated dependencies [faf98f5]
+  - @checkstack/backend-api@0.29.0
+  - @checkstack/common@0.20.0
+  - @checkstack/healthcheck-common@1.12.0
+
 ## 0.3.5
 
 ### Patch Changes

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@checkstack/healthcheck-postgres-backend",
-  "version": "0.3.5",
+  "version": "0.4.1",
   "type": "module",
   "main": "src/index.ts",
   "checkstack": {
@@ -14,9 +14,9 @@
     "pack": "bunx @checkstack/scripts plugin-pack"
   },
   "dependencies": {
-    "@checkstack/backend-api": "0.28.0",
-    "@checkstack/common": "0.19.0",
-    "@checkstack/healthcheck-common": "1.11.0",
+    "@checkstack/backend-api": "0.29.1",
+    "@checkstack/common": "0.21.0",
+    "@checkstack/healthcheck-common": "1.13.0",
     "pg": "^8.11.0"
   },
   "devDependencies": {
@@ -24,7 +24,7 @@
     "@types/pg": "^8.11.0",
     "typescript": "^5.0.0",
     "@checkstack/tsconfig": "0.0.7",
-    "@checkstack/scripts": "0.7.0"
+    "@checkstack/scripts": "0.7.2"
   },
   "description": "Checkstack healthcheck-postgres-backend plugin",
   "author": {

package/src/query-collector.ts

@@ -43,6 +43,7 @@ const queryResultSchema = healthResultSchema({
     // fire on routine data growth, so it is off by default. Still chartable
     // and opt-in per check.
     "x-anomaly-enabled": false,
+    "x-chart-priority": 30,
   }),
   executionTimeMs: healthResultNumber({
     "x-chart-type": "line",
@@ -54,12 +55,16 @@ const queryResultSchema = healthResultSchema({
     "x-anomaly-confirmation-window": 3,
     "x-anomaly-min-absolute-delta": 50,
     "x-anomaly-min-relative-delta": 0.5,
+    "x-chart-priority": 10,
   }),
   success: healthResultBoolean({
     "x-chart-type": "boolean",
     "x-chart-label": "Success",
+    "x-chart-true-label": "successful",
+    "x-chart-false-label": "failing",
     "x-anomaly-enabled": true,
     "x-anomaly-direction": "dominance",
+    "x-chart-good-direction": "up",
   }),
 });
 
@@ -79,6 +84,7 @@ const queryAggregatedFields = {
     "x-anomaly-confirmation-window": 3,
     "x-anomaly-min-absolute-delta": 50,
     "x-anomaly-min-relative-delta": 0.5,
+    "x-chart-priority": 10,
   }),
   successRate: aggregatedRate({
     "x-chart-type": "gauge",

package/src/strategy.ts

@@ -14,6 +14,7 @@ import {
   mergeMinMax,
   z,
   configString,
+  configSecret,
   configNumber,
   configBoolean,
   type ConnectedClient,
@@ -52,7 +53,7 @@ export const postgresConfigSchema = baseStrategyConfigSchema.extend({
     .describe("PostgreSQL port"),
   database: configString({}).describe("Database name"),
   user: configString({}).describe("Database user"),
-  password: configString({ "x-secret": true }).describe("Database password"),
+  password: configSecret({ id: "password" }).describe("Database password"),
   ssl: configBoolean({}).default(false).describe("Use SSL connection"),
 });
 
@@ -66,8 +67,11 @@ const postgresResultSchema = healthResultSchema({
   connected: healthResultBoolean({
     "x-chart-type": "boolean",
     "x-chart-label": "Connected",
+    "x-chart-true-label": "connected",
+    "x-chart-false-label": "disconnected",
     "x-anomaly-enabled": true,
     "x-anomaly-direction": "dominance",
+    "x-chart-good-direction": "up",
   }),
   connectionTimeMs: healthResultNumber({
     "x-chart-type": "line",
@@ -79,6 +83,7 @@ const postgresResultSchema = healthResultSchema({
     "x-anomaly-confirmation-window": 3,
     "x-anomaly-min-absolute-delta": 50,
     "x-anomaly-min-relative-delta": 0.5,
+    "x-chart-priority": 10,
   }),
   error: healthResultString({
     "x-chart-type": "status",
@@ -103,6 +108,7 @@ const postgresAggregatedFields = {
     "x-anomaly-confirmation-window": 3,
     "x-anomaly-min-absolute-delta": 50,
     "x-anomaly-min-relative-delta": 0.5,
+    "x-chart-priority": 10,
   }),
   maxConnectionTime: aggregatedMinMax({
     "x-chart-type": "line",
@@ -113,6 +119,7 @@ const postgresAggregatedFields = {
     // alerts. Average connection time already covers the latency-saturation
     // signal, so the max is off by default and remains chartable.
     "x-anomaly-enabled": false,
+    "x-chart-good-direction": "down",
   }),
   successRate: aggregatedRate({
     "x-chart-type": "gauge",
@@ -133,6 +140,8 @@ const postgresAggregatedFields = {
     // failures as a normalized percent, so this absolute twin is off by default
     // to avoid duplicate, volume-sensitive alerts.
     "x-anomaly-enabled": false,
+    "x-chart-good-direction": "down",
+    "x-chart-priority": 90,
   }),
 };