@checkstack/anomaly-frontend 0.5.6 → 0.5.8

package/CHANGELOG.md

@@ -1,5 +1,42 @@
 # @checkstack/anomaly-frontend
 
+## 0.5.8
+
+### Patch Changes
+
+- @checkstack/healthcheck-frontend@0.23.8
+
+## 0.5.7
+
+### Patch Changes
+
+- 0b6f01b: feat(anomaly): contribute anomaly signals to the backend system.issues aggregator
+
+  The anomaly plugin now registers a `system.issues` contributor (sourceId
+  `anomaly`) from its backend `init`, so the AI assistant surfaces confirmed
+  anomalies and suspicious states alongside incidents, SLOs, health checks, and
+  dependency problems.
+
+  The contributor enforces its own `anomaly_feed.read` access gate (returning an
+  empty map - never throwing - when the principal lacks access; service users are
+  trusted), then reads the current problem rows for every system from the shared,
+  durable `anomalies` table via a new global `getActiveSignalAnomalies` service
+  method (state = anomaly | suspicious, suppressed rows excluded). The answer is
+  therefore identical on every pod, and only systems with a current problem appear
+  in the result.
+
+  The row->signal mapping (source/tone/label/detail/href/accessRule/iconName) is
+  extracted into a new pure `deriveAnomalySignals` deriver in
+  `@checkstack/anomaly-common`, shared by both the backend contributor and the
+  frontend `AnomalySignalsFiller` so the two surfaces stay in lockstep. The
+  frontend filler now delegates to that deriver with unchanged behavior.
+
+- Updated dependencies [0b6f01b]
+- Updated dependencies [0b6f01b]
+  - @checkstack/anomaly-common@1.4.0
+  - @checkstack/healthcheck-common@1.6.0
+  - @checkstack/healthcheck-frontend@0.23.7
+
 ## 0.5.6
 
 ### Patch Changes

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@checkstack/anomaly-frontend",
-  "version": "0.5.6",
+  "version": "0.5.8",
   "license": "Elastic-2.0",
   "type": "module",
   "main": "src/index.tsx",
@@ -13,12 +13,12 @@
     "lint:code": "eslint . --max-warnings 0"
   },
   "dependencies": {
-    "@checkstack/anomaly-common": "1.3.4",
+    "@checkstack/anomaly-common": "1.4.0",
     "@checkstack/catalog-common": "2.3.4",
     "@checkstack/common": "0.15.0",
     "@checkstack/frontend-api": "0.9.0",
-    "@checkstack/healthcheck-common": "1.5.4",
-    "@checkstack/healthcheck-frontend": "0.23.6",
+    "@checkstack/healthcheck-common": "1.6.0",
+    "@checkstack/healthcheck-frontend": "0.23.8",
     "@checkstack/notification-common": "1.3.3",
     "@checkstack/notification-frontend": "0.5.5",
     "@checkstack/signal-frontend": "0.2.4",

package/src/components/AnomalySignalsFiller.tsx

@@ -3,10 +3,14 @@ import { usePluginClient, type SlotContext } from "@checkstack/frontend-api";
 import { resolveRoute } from "@checkstack/common";
 import {
   SystemSignalsSlot,
-  type SystemSignal,
   type SystemSignalsMap,
 } from "@checkstack/catalog-common";
-import { AnomalyApi } from "@checkstack/anomaly-common";
+import {
+  AnomalyApi,
+  deriveAnomalySignals,
+  ANOMALY_SIGNAL_SOURCE_ID,
+  type AnomalySignalRow,
+} from "@checkstack/anomaly-common";
 import {
   healthcheckRoutes,
   healthCheckAccess,
@@ -14,14 +18,12 @@ import {
 
 type Props = SlotContext<typeof SystemSignalsSlot>;
 
-const SOURCE_ID = "anomaly";
-
 /**
  * Reports confirmed anomalies and suspicious states as dashboard signals.
  * Reuses the two globally-deduped anomaly queries (the same ones the badge
- * uses) and emits one signal per anomaly for systems in the overview, deep-
- * linking to the affected check's history. Headless filler for
- * {@link SystemSignalsSlot}.
+ * uses) and the shared {@link deriveAnomalySignals} mapper - the SAME mapper the
+ * backend `system.issues` contributor runs - so frontend and backend signals
+ * stay identical. Headless filler for {@link SystemSignalsSlot}.
  */
 export const AnomalySignalsFiller: React.FC<Props> = ({
   systemIds,
@@ -39,46 +41,31 @@ export const AnomalySignalsFiller: React.FC<Props> = ({
   );
 
   const signals = useMemo<SystemSignalsMap>(() => {
-    const result: SystemSignalsMap = {};
     const inOverview = new Set(systemIds);
+    const rows: AnomalySignalRow[] = [...confirmed, ...suspicious]
+      .filter((a) => inOverview.has(a.systemId))
+      .map((a) => ({
+        systemId: a.systemId,
+        configurationId: a.configurationId,
+        fieldPath: a.fieldPath,
+        startedAt: a.startedAt,
+        state: a.state,
+      }));
 
-    const add = (
-      systemId: string,
-      configurationId: string,
-      fieldPath: string,
-      startedAt: string,
-      tone: SystemSignal["tone"],
-      label: string,
-    ) => {
-      if (!inOverview.has(systemId)) return;
-      const signal: SystemSignal = {
-        source: SOURCE_ID,
-        tone,
-        label,
-        detail: fieldPath,
-        href: resolveRoute(healthcheckRoutes.routes.historyDetail, {
-          systemId,
-          configurationId,
+    return deriveAnomalySignals({
+      rows,
+      buildHref: (row) =>
+        resolveRoute(healthcheckRoutes.routes.historyDetail, {
+          systemId: row.systemId,
+          configurationId: row.configurationId,
         }),
-        // The history detail page is gated; render as text for users without it.
-        accessRule: healthCheckAccess.details,
-        since: new Date(startedAt).toISOString(),
-        iconName: "ChartSpline",
-      };
-      (result[systemId] ??= []).push(signal);
-    };
-
-    for (const a of confirmed) {
-      add(a.systemId, a.configurationId, a.fieldPath, a.startedAt, "warn", "Anomaly detected");
-    }
-    for (const a of suspicious) {
-      add(a.systemId, a.configurationId, a.fieldPath, a.startedAt, "info", "Suspicious behaviour");
-    }
-    return result;
+      // The history detail page is gated; render as text for users without it.
+      accessRule: healthCheckAccess.details,
+    });
   }, [confirmed, suspicious, systemIds]);
 
   useEffect(() => {
-    onSignals(SOURCE_ID, signals);
+    onSignals(ANOMALY_SIGNAL_SOURCE_ID, signals);
   }, [signals, onSignals]);
 
   return null;