The threshold affects the visibility of a given logger. When a log statement is called, e.g. flog.debug('foo'), futile.logger compares the threshold of the logger with the level implied in the log command (in this case DEBUG). If the log level is at or higher in priority than the logger threshold, a message will print. Otherwise the command will silently return.
● Data Source:
CranContrib
● Keywords: data
● Alias: flog.threshold
●
0 images
This function integrates futile.logger with the error and warning system so problems can be caught both in the standard R warning system, while also being emitted via futile.logger.
● Data Source:
CranContrib
● Keywords: data
● Alias: ftry
●
0 images
This package implements a logging system inspired by log4j. The basic idea of layouts, appenders, and loggers is faithful to log4j, while the implementation and idiom is all R. This means that support for hierarchical loggers, custom appenders, custom layouts is coupled with a simple and intuitive functional syntax.
Provides functions for writing log messages and managing loggers. Typically only the flog.[trace|debug|info|warn|error|fatal] functions need to be used in conjunction with flog.threshold to interactively change the log level.
● Data Source:
CranContrib
● Keywords: data
● Alias: flog.debug, flog.error, flog.fatal, flog.info, flog.logger, flog.trace, flog.warn
●
0 images
In the event that you no longer wish to have a logger registered, use this function to remove it. Then any references to this logger will inherit the next available logger in the hierarchy.
● Data Source:
CranContrib
● Keywords: data
● Alias: flog.remove
●
0 images