There is some flexibility in the colorSpec logging level and format.
Logging output goes to
stderr(), just like the message stream;
sink() (and the pitfalls of using it).
The levels are:
"FATAL", "ERROR", "WARN", "INFO", "DEBUG", and
"TRACE" - the usual ones from Log4j.
The initial level is
"FATAL" event usually means an internal package error.
colorSpec.loglevel an initial letter is sufficient.
The format is given by a string with standard Log4j conversion specifications:
||the date/time of the logging event.||
||the level of the logging event|
||namespace where event occurred|
||function where event occurred|
||the message itself|
If the this option is
TRUE (the default),
a log event with level
"ERROR" stops execution;
otherwise, execution keeps going.
For interactive use,
TRUE is probably better.
For long batch jobs,
FALSE might be appropriate,
since then a single error may not force a complete repeat.
"FATAL" event always stops execution.
Wikipedia. Log4j. http://en.wikipedia.org/wiki/Log4j
1 2 3 4
Add the following code to your website.
For more information on customizing the embed code, read Embedding Snippets.