add additional heartbeat tests

This commit is contained in:
Alex Holliday committed 2026-04-14 11:31:09 -07:00
1 parent fd8dce8abe
commit e8bcfdd21d
2 files changed
+77

No files matched your search

@@ -72,5 +72,31 @@ describe("Heartbeat job: down detection", () => {
const storedMonitor = await h.monitorsRepo.findById("mon-1", "team-1");
expect(storedMonitor.status).toBe("up");
expect(h.incidentsRepo.getAll()).toHaveLength(0);
// Regression guard for #3438: a sub-threshold blip must produce NO notification
// dispatches. Before PR #3505, a failing check below threshold silently wrote
// status="down" and the next passing check fired a spurious "Recovered" event.
expect(h.notificationsService.handleNotifications).not.toHaveBeenCalled();
});
it("fires zero notifications on a sub-threshold blip (regression #3438)", async () => {
// Dedicated end-to-end guard for the #3438 bug. Distinct from "stays up when
// failures are below threshold" because it pins the notification-dispatch
// contract independently of status/incident assertions, so a future refactor
// that reintroduces the silent-down-write can't sneak past by happening to
// leave status and incidents in the right shape.
const monitor = makeMonitor();
h.monitorsRepo.seed(monitor);
// Failing check below threshold (window [t,t,t,t,f], 20%)
h.setNextResponse(false, 503);
await h.heartbeatJob(monitor);
// Passing check — pre-fix, this is where the spurious "Recovered" fired
h.setNextResponse(true, 200);
await h.heartbeatJob(monitor);
expect((await h.monitorsRepo.findById("mon-1", "team-1")).status).toBe("up");
expect(h.incidentsRepo.getAll()).toHaveLength(0);
expect(h.notificationsService.handleNotifications).not.toHaveBeenCalled();
});
});
@@ -123,6 +123,57 @@ describe("Heartbeat job: hardware threshold breach", () => {
expect(incidents[0].resolutionType).toBe("automatic");
});
it("transitions breached hardware monitor to down when reachability also fails", async () => {
// A hardware monitor currently in "breached" state starts failing its reachability
// checks enough to cross the statusWindow threshold. "down" must take precedence
// over "breached" — when both conditions are true, the user wants the escalated
// alert. Unit-covered in statusService.test.ts via computeReachability; this is
// the end-to-end counterpart that exercises the full heartbeat path including
// incident-lifecycle handling.
const monitor = makeMonitor({
type: "hardware",
status: "breached",
cpuAlertThreshold: 80,
cpuAlertCounter: 0,
memoryAlertThreshold: 100,
memoryAlertCounter: 5,
diskAlertThreshold: 100,
diskAlertCounter: 5,
tempAlertThreshold: 100,
tempAlertCounter: 5,
selectedDisks: [],
// Window is fully healthy — the monitor is breached from hardware metrics,
// not from reachability. The test drives the window from clean → failing.
statusWindow: [true, true, true, true, true],
});
h.monitorsRepo.seed(monitor);
// Seed an active breached incident matching the initial state.
await h.incidentsRepo.create({
monitorId: "mon-1",
teamId: "team-1",
status: true,
statusCode: 9999,
message: "CPU: 90% (threshold: 80%)",
});
// Drive reachability failure: 3 consecutive failing heartbeats.
// Window evolves: [t,t,t,t,t] → [t,t,t,t,f] (20%) → [t,t,t,f,f] (40%) → [t,t,f,f,f] (60%)
// At 60% >= threshold, and current status "breached" !== "down", reachability fires.
// Reachability sends HTTP-shaped responses with no hardware payload, so the
// hardware block is correctly skipped for these checks.
h.setNextResponse(false, 503);
for (let i = 0; i < 3; i++) {
await h.heartbeatJob(monitor);
}
const stored = await h.monitorsRepo.findById("mon-1", "team-1");
expect(stored.status).toBe("down");
// Notification dispatch must have fired for the transition.
expect(h.notificationsService.handleNotifications).toHaveBeenCalled();
});
it("does not create duplicate incidents while remaining breached", async () => {
const monitor = makeMonitor({
type: "hardware",