Job output and warnings
themao opened this issue · comments
Hello Kamisama,
I have noticed that there's no job output logging. Is it possible to pass via Monolog to Mongo? And is it a desired functionality? Because in my project we need to see the output of the script.
And I also see that warnings/notices are not handled by try/catch blocks, so I've made a small workaround that replaces them with exceptions (using events). How do you think, is that a good behavior and is it worth forking and creating pull-request? Or better solution will be just to buffer the output and send it to ResqueBoard as I described above?
Thanks.
So you want to send the log to ResqueBoard, and somewhere else at the same time ?
No, just to ResqueBoard. The stdout & stderr of the job.
I don't quite understand. You want to redirect all stdout and stderr to a file ? Because they're not sent to Cube ?
Yes, the output of the script that is echoed or printed. And not to a file, but to the Cube, to see it in the Resqueboard.
I don't quite understand what you want, can you explain more in details ?
Well, when you click on a successfully finished job here http://resque.kamisama.me/jobs/view, you can see only args that were passed. What I want is to see the output of the job - everything that the script echo'ed during the execution.
I see.
How are you starting/managing your workers ?
From bash console.
Mhmmm ... It's a functionality that should be implemented on the php-resque side.
You can try opening a ticket over there, and propose logging the job output.
Yes, indeed. Sorry for mixing up the repos, but I also use your fork of php-resque (php-resque-ex). I will create an issue there.
I think you can directly ask it on php-resque repo, instead of the fork. The fork will be merged back into the original soon.