HackerNews中文版

我遇到了一个问题，我的定时任务“成功”了，但实际上并没有正确执行它们的工作。例如： - 备份定时任务运行，退出代码为0，但生成了空文件。 - 数据同步成功完成，但只处理了部分记录。 - 报告生成器完成，但输出的数据不完整。日志显示一切正常，但结果却是错误的。实际上，错误可能在日志的某个地方，但谁会主动检查日志呢？我可不想每天都翻阅日志文件，看看是否有什么悄悄失败了。我尝试过： - 在脚本中添加验证——有效，但仍然需要检查日志。 - 使用Webhook警报——但你必须为每个脚本编写连接器。 - 错误监控工具——但它们只捕捉异常，而不是错误结果。最终，我构建了一个简单的监控工具，它监视作业结果，而不仅仅是执行状态——你将实际结果（文件大小、记录数等）发送给它，如果有异常，它会发出警报。这样就无需翻阅日志了。但我很好奇：你们都是怎么处理这个问题的？你们真的定期检查日志吗，还是有其他方法可以主动提醒你们结果与预期不符？

查看原文

I've been running into this issue where my cron jobs "succeed" but don't actually do their job correctly.For example:Backup cron runs, exit code 0, but creates empty filesData sync completes successfully but only processes a fraction of recordsReport generator finishes but outputs incomplete dataThe logs say everything's fine, but the results are wrong. Actually, the errors are probably in the logs somewhere, but who checks logs proactively? I'm not going through log files every day to see if something silently failed.I've tried:Adding validation in scripts - works, but you still need to check the logsWebhook alerts - but you have to write connectors for every scriptError monitoring tools - but they only catch exceptions, not wrong resultsI ended up building a simple monitoring tool that watches job results instead of just execution - you send it the actual results (file size, count, etc.) and it alerts if something's off. No need to dig through logs.But I'm curious: how do you all handle this? Are you actually checking logs regularly, or do you have something that proactively alerts you when results don't match expectations?

问HN：你们是如何验证定时任务是否按预期执行的？