@checkstack/healthcheck-http-backend 0.7.0 → 0.7.2

package/CHANGELOG.md

@@ -1,5 +1,62 @@
 # @checkstack/healthcheck-http-backend
 
+## 0.7.2
+
+### Patch Changes
+
+- Updated dependencies [390d9cf]
+- Updated dependencies [fc64fad]
+- Updated dependencies [9d30324]
+  - @checkstack/backend-api@0.30.0
+  - @checkstack/healthcheck-common@1.14.0
+
+## 0.7.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.7.0
 
 ### Minor Changes

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@checkstack/healthcheck-http-backend",
-  "version": "0.7.0",
+  "version": "0.7.2",
   "type": "module",
   "main": "src/index.ts",
   "checkstack": {
@@ -14,16 +14,16 @@
     "pack": "bunx @checkstack/scripts plugin-pack"
   },
   "dependencies": {
-    "@checkstack/backend-api": "0.29.0",
-    "@checkstack/healthcheck-common": "1.12.0",
+    "@checkstack/backend-api": "0.30.0",
+    "@checkstack/healthcheck-common": "1.14.0",
     "jsonpath-plus": "^10.3.0",
-    "@checkstack/common": "0.20.0"
+    "@checkstack/common": "0.21.0"
   },
   "devDependencies": {
     "@types/bun": "^1.0.0",
     "typescript": "^5.0.0",
     "@checkstack/tsconfig": "0.0.7",
-    "@checkstack/scripts": "0.7.1"
+    "@checkstack/scripts": "0.7.2"
   },
   "description": "Checkstack healthcheck-http-backend plugin",
   "author": {

package/src/request-collector.ts

@@ -81,6 +81,7 @@ const requestResultSchema = healthResultSchema({
   statusCode: healthResultNumber({
     "x-chart-type": "counter",
     "x-chart-label": "Status Code",
+    "x-chart-priority": 30,
     // Off by default: the raw status code is an identifier, not a quantity
     // with a meaningful baseline. Legitimate shifts (200 -> 301/302 redirects,
     // content negotiation) are not problems, while real availability loss is
@@ -97,6 +98,7 @@ const requestResultSchema = healthResultSchema({
     "x-chart-type": "line",
     "x-chart-label": "Response Time",
     "x-chart-unit": "ms",
+    "x-chart-priority": 10,
     "x-anomaly-enabled": true,
     "x-anomaly-direction": "lower-is-better",
     "x-anomaly-sensitivity": 2,
@@ -109,11 +111,16 @@ const requestResultSchema = healthResultSchema({
     "x-chart-type": "counter",
     "x-chart-label": "Body Length",
     "x-chart-unit": "bytes",
+    "x-chart-priority": 90,
     "x-anomaly-enabled": false,
   }),
   success: healthResultBoolean({
     "x-chart-type": "boolean",
     "x-chart-label": "HTTP Success",
+    "x-chart-true-label": "successful",
+    "x-chart-false-label": "failing",
+    "x-chart-priority": 20,
+    "x-chart-good-direction": "up",
     "x-anomaly-enabled": true,
     "x-anomaly-direction": "dominance",
   }),
@@ -127,6 +134,7 @@ const requestAggregatedFields = {
     "x-chart-type": "line",
     "x-chart-label": "Avg Response Time",
     "x-chart-unit": "ms",
+    "x-chart-priority": 10,
     "x-anomaly-enabled": true,
     "x-anomaly-direction": "lower-is-better",
     // Latency: bias toward fewer false positives. Require several consecutive
@@ -141,6 +149,7 @@ const requestAggregatedFields = {
     "x-chart-type": "gauge",
     "x-chart-label": "Success Rate",
     "x-chart-unit": "%",
+    "x-chart-priority": 20,
     "x-anomaly-enabled": true,
     "x-anomaly-direction": "higher-is-better",
     // Availability percent: the canonical saturation/failure signal. Debounce

package/src/strategy.ts

@@ -200,6 +200,8 @@ const httpAggregatedFields = {
   errorCount: aggregatedCounter({
     "x-chart-type": "counter",
     "x-chart-label": "Errors",
+    "x-chart-priority": 90,
+    "x-chart-good-direction": "down",
     // Off by default: a raw per-bucket error COUNT scales with how many runs
     // land in the bucket, so it has no stable baseline and drifts with traffic
     // volume. The percent form of the same signal (`successRate`) is the one