How are people logging with Dancer2
I'm looking at logging and notice that there don't appear to be any handlers other than the core ones. Then I look at Dancer2::Logger::File and see these issues: * log_path is documented but no code actually uses it * holds an open file-handle. No flush/reopen on a signal, so log rotation means restarting the whole app So what are people using Dancer2 actually doing for logging? Just Console grabbed by a supervisor daemon? David -- David Golden <xdg@xdg.me> Take back your inbox! → http://www.bunchmail.com/ Twitter/IRC: @xdg
Hi, On Thu, Jun 27, 2013 at 12:50 AM, David Golden <xdg@xdg.me> wrote:
I'm looking at logging and notice that there don't appear to be any handlers other than the core ones.
Then I look at Dancer2::Logger::File and see these issues:
* log_path is documented but no code actually uses it
* holds an open file-handle. No flush/reopen on a signal, so log rotation means restarting the whole app
So what are people using Dancer2 actually doing for logging? Just Console grabbed by a supervisor daemon?
Deployed two apps on Dancer2 to production last week, and went through the same process. Due to time constraints I ended up logging to console and used multilog to handle log rotation. So yes, Console grabbed by a superviser daemon. Bye, -- Pedro Melo @pedromelo http://www.simplicidade.org/ xmpp:melo@simplicidade.org mailto:melo@simplicidade.org
On Thu, Jun 27, 2013 at 1:49 AM, Pedro Melo <melo@simplicidade.org> wrote:
Deployed two apps on Dancer2 to production last week, and went through the same process. Due to time constraints I ended up logging to console and used multilog to handle log rotation.
Looking closer, the File logger is using append mode -- sadly without locking -- so I think that if I patch it to lock and fix the documentation, it might actually be usable. Then logrotate with copy/truncate mode would do. -- David Golden <xdg@xdg.me> Take back your inbox! → http://www.bunchmail.com/ Twitter/IRC: @xdg
participants (2)
-
David Golden -
Pedro Melo