SK
That observability point is the one most teams learn the hard way, because a cron job that fails quietly looks exactly like a cron job that has nothing to do. The detail I would add is alerting on a missed run, not just a failed one, since a job that never starts leaves no error behind at all. Do you treat a missed run as its own alert, or fold it into the same failure channel?
