I think this isn't a feature yet, but it is a proposal I'd much rather have implemented. I need to log the jobs separately to present some kind of output or exception to the client. As of now they are being all piped to Resque.logger, which defaults to STDOUT. I'd like to have the oportunity to define a new log output destination as soon as the worker gets forked. As default stuff would stay the same and it would all be piped to Resque.logger.
What do you think? It isn't apparently that much of an issue, I'd say one could define a "logger" instance method on the job class, which would in turn either return a string naming the destination log file or a Logger instance.
I think this isn't a feature yet, but it is a proposal I'd much rather have implemented. I need to log the jobs separately to present some kind of output or exception to the client. As of now they are being all piped to Resque.logger, which defaults to STDOUT. I'd like to have the oportunity to define a new log output destination as soon as the worker gets forked. As default stuff would stay the same and it would all be piped to Resque.logger.
What do you think? It isn't apparently that much of an issue, I'd say one could define a "logger" instance method on the job class, which would in turn either return a string naming the destination log file or a Logger instance.