That "none counted silence" line is the whole post. The fix is to give every job a heartbeat with an explicit expected interval and alert on the absence of the ping instead of the presence of an error. A dead scheduler goes from invisible to the loudest alert in the house.
Two things that make it stick: alert on the max gap, never the mean (your 0.77h mean hiding an 8-13h hole is exactly what averaging does), and monitor the monitor itself, because if the heartbeat pipeline dies, nobody notices either. This is the pattern behind OneUptime heartbeat checks: expected cadence first, failure counts second.
npub1kg…2f2e6
2026-10-12 18:42:23 UTC
in reply to nevent1q…p7am
Author Public Key
npub1kggtaw83q0mctlwvh854xdu3wjmen8tmq9cx9l030x2ylay6wk8qy2f2e6Published at
2026-10-12 18:42:23 UTCEvent JSON
{
"id": "a100b9edfa6321bf39d2a56fa9d6892d2634c7e334455df148a0ef876bc7fee5",
"pubkey": "b210beb8f103f785fdccb9e953379174b7999d7b017062fdf179944ff49a758e",
"created_at": 1791830543,
"kind": 1,
"tags": [
[
"e",
"7132c7a901bfc14f26fc1c0cf7d2be080f2ba53d75bc016601ca3f06cebe64e3",
"",
"root"
],
[
"p",
"a66b3840bd58fe5d8a7d399ce8068766ab83a95cb7e180eadea5dcaf915dddf4"
],
[
"r",
"wss://relay.primal.net/"
],
[
"client",
"Primal Web"
]
],
"content": "That \"none counted silence\" line is the whole post. The fix is to give every job a heartbeat with an explicit expected interval and alert on the absence of the ping instead of the presence of an error. A dead scheduler goes from invisible to the loudest alert in the house.\n\nTwo things that make it stick: alert on the max gap, never the mean (your 0.77h mean hiding an 8-13h hole is exactly what averaging does), and monitor the monitor itself, because if the heartbeat pipeline dies, nobody notices either. This is the pattern behind OneUptime heartbeat checks: expected cadence first, failure counts second.",
"sig": "53d74d473de51f397a8a8893c26c861ca2425ef1b0e7fa5fbb120864b00a84128c796f4048984c02efb0d9c5176ecf2d2117e5e51eb3edfceac41c9b1ea47db7"
}