We need to get in place a better mechanism to handle results of DB audit, as there are multiple problems with our current approach. The most obvious is that it isn't working, currently. But we also need to consider things like concurrency, and a reusable interface for initiating other notifications. @nwinklareth had some ideas about this, I think. One of them was to generate a certain file on failure, and then poll for the existence of this file with cron, I think?
We need to get in place a better mechanism to handle results of DB audit, as there are multiple problems with our current approach. The most obvious is that it isn't working, currently. But we also need to consider things like concurrency, and a reusable interface for initiating other notifications. @nwinklareth had some ideas about this, I think. One of them was to generate a certain file on failure, and then poll for the existence of this file with cron, I think?