On 4 January 2017 at 19:12, Andrew Beverley <andy@...> wrote:

On Wed, 4 Jan 2017 Nathan Bailey wrote:
> 1. Add logging information to my yml

Yes, although if you just want to test it initially, then you don't
need any config and any messages will go to STDERR (I think).

They happily print to STDERR, they just don't print to the log file :-)

I have:

# The log level for this environment. Log warning and error messages [ presumably this doesn't conflict with the LogReport log levels? ]

log: 'info'

logger: "LogReport"

engines:

  logger:

    LogReport:

      log_format: %a%i%m

      app_name: AppName

      dispatchers:

      logfile:              # "default" dispatcher stays open as well

      type: FILE

      to: /path/filename.log

      charset: utf-8

      mode: DEBUG

 

> 2. Add use Log::Report ();

This is no longer needed (sorry, I thought the docs had been updated).

Okay, so I just have:

use Dancer2;

...

use Dancer2::Plugin::LogReport mode => 'DEBUG'; # '3' or 'DEBUG'

in my main route handler module.

With this config, nothing is being written to my log file (ie. normal 'info' messages that were getting written with:

logger: "File"

 

engines:

  logger:

    File:

      log_dir: "/path"

      file_name: "filename.log"

(now removed and replaced with above) are no longer getting written. I have a 'trace' and 'info' in a non-Dancer module that is writing to stderr.

Log::Report maintains some global space that all messages go to. When a
message is logged (regardless of where it is logged from) that will
trigger the logging code in the Dancer plugin. The Dancer plugin knows
your config, so it all Just Works.

Nifty! Presumably module-based unit tests need to include Log::Report with some suitable config/dispatcher?

thanks,

Nathan