Chain healthy and every monitoring layer running with no alerts
A status check found Satsuma's chain healthy: best block 4,776,228, a finality lag of 2 blocks and 30 blocks per minute. The summary of the check put it in one line: "The chain is healthy and every monitoring layer is running with nothing firing."
The monitoring behind that line was set up the same day. Watchdogs on each of the three nodes run with 0 failing checks each. A separate monitor box watches 8 of 8 targets as up, with no alerts firing, and runs jobs for an RPC probe, a dry run of the write path that moves no funds, chain-event alerts, uptime and a daily digest. Push alerts come from the public status page, which is live with an empty incident list, and reach 2 subscribed devices; a dead man's switch raises an alarm if the monitoring itself goes quiet.
Around it, the explorer now decodes transaction inputs and event logs, the website links the status page, and a parking wildcard record was removed from DNS. For this site, the CI build artifact is now kept for 3 days instead of 90, and the stored artifacts were cleared.
A separate runtime experiment sits on a branch, parked. The first daily digest is scheduled for 09:00 UTC.
- ci: keep the build artifact for 3 days instead of 90This site
- ci: keep the build artifact for 3 days instead of 90This site
- The first daily digest is scheduled for 09:00 UTC.