right now cron spam is mostly unlooked at, however there might be real issues lurking
I think one of the problems is that there is no aggregation/deduplication so the same issue ends up with many emails and thus ignored, one way to tackle this would be to provide aggregation/deduplication so the real issue is easy to spot (and possibly fix) for example experimenting with https://github.com/KMNR/raven-cron would be a good start. In short cron wouldn't be reporting output via mail but rather via sentry which would then collate based on e.g. the command line