An odd question? Perhaps not. When you work with multiple systems, I'm sure you've all hit the same issues as I have. Sometimes, the output from System X never made it to downstream System Y.
Now, if you're using a nice messaging system then there may well be some form of logic governing the retrying. But what if it's simpler than that. What if you are simply relying on the upstream system dropping a file in a shared location?
You (and by you, I mean the Monitoring Guru that you surely are) get asked to warn people that a file hasn't arrived! Fun huh?
To solve this issue, I created an App to help me - I thought I'd pass it around to see you could use it to :) It's called the FileScannerApp and it's on GitHub now.
It's very very simple.
1. You give it a folder you want to watch.
2. Every so often, it returns a small log, detailing the contents, the modified date of each item and the size.
3. Logscape takes that data and extrapolates the time since modified (in hours, minutes or days) as well as the size (in KB,MB,GB).
Simple stuff.
But you can get some juicy alerts going once you have that info. You can set alerts if the delta change of the file size increases beyond a certain limit (i.e. My log is getting too big, too fast... something is amiss).
You can also get it to check if the output file of system X has been modified in the last 24 hours - and then alert you if it hasn't!
If this sounds useful, go grab it. Any improvements, stick them on!