The current logging architecture is routed through RabbitMQ. I tried with the approach you have suggested but the log records where skipped silently and my custom ```emit``` callback never called. I could not figure out why.

Certainly, once that we have addressed the problem of supervising jobs from oq-engine-server it would be easier to refactor this. Then, my opinion is to keep this approach as it is but mark it as a technical debt. https://bugs.launchpad.net/oq-engine/+bug/1250864