Your job "succeeded" but did nothing how do you even catch that?
Had an interesting conversation recently about queue monitoring in Laravel. Someone came to me with a production case: a job was supposed to create 10,000 users, created 400, and still reported as successful. No errors, no exceptions, everything green. And I realized, right now my system can't even tell whether a job actually did what it was supposed to. I started looking at other monitoring tools, and most of them just say "it ran" or "it failed". But what about when it runs, doesn't crash, and just ... does the wrong thing?
Started thinking about tracking execution time baselines, if a job that normally takes 30 seconds suddenly finishes in 2, something's probably off. But that only catches the obvious cases. The harder question is: should the job itself validate its own result? Like "I was supposed to create 10,000 records, I created 400, that's not right"? Or is that already business logic and doesn't belong in monitoring?
Because the moment you start checking results, you're basically writing tests for every job, and that feels like a rabbit hole.
Curious how you guys handle this. Do you just trust "no error = success" or do you actually verify what happened after the job ran?
Is it even worth digging into this or is it overengineering?
GitHub: https://github.com/RomaLytar/yammi-jobs-monitoring-laravel
