The hardware and bandwidth for this mirror is donated by dogado GmbH, the Webhosting and Full Service-Cloud Provider. Check out our Wordpress Tutorial.
If you wish to report a bug, or if you are interested in having us mirror your free-software or open-source project, please feel free to contact us at mirror[@]dogado.de.

Overview

futile.logger is a logging utility for R. Originally built based on log4j, the latest version introduces a new API that is more consistent with R idioms. In practice this means an interface that works equally well in the shell for interactive use and also in scripts for system use.

The underlying concepts of log4j still exist, e.g. loggers, appenders, and formatters. There continues to be a hierarchical system for logger. In addition, there is now automatic package scoping, which means that packages are given their own logger namespace so you can interactively turn on and off logging for specific packages.

Also included is formatting logic to log list objects (which includes data.frames) in a smart way.

Usage

Out of the box, the default ROOT logger logs to the console with threshold set to INFO.

flog.info("Hello, %s", "world")

# This won't print by default
flog.debug("Goodbye, %s", "world")

# Change the log level to debug and try again
flog.threshold(DEBUG)
flog.debug("Goodbye, %s", "world")

# Keep an alternate logger at WARN
flog.threshold(WARN, name='quiet')

# This won't print since it's using the logger named 'quiet'!
flog.debug("Goodbye, %s", "world", name='quiet')

Loggers

A logger is simply a namespace bound to a threshold, an appender, and a formatter. Loggers are configured automatically whenever they are referenced (for example when changing the threshold) inheriting the settings of the root logger. To explicitly create a logger call log.logger().

flog.logger("tawny", WARN, appender=appender.file('tawny.log'))

To remove a logger, use log.remove(). If no such logger exists, the command is safely ignored.

flog.remove("tawny")

Thresholds

The logger threshold determines what will be logged for a given logger. Use this function to retrieve and also change this threshold.

# Get the logging threshold for the ROOT logger
flog.threshold()

The default logger is ROOT. To change the threshold of a different logger, specify the logger argument with a string that represents the logger. Note that a log.(debug|info|warn|error) command running from a package will automatically be associated with a logger with the name of the package. This structure means you can change the log level for a specific package as necessary.

# Set root logger to DEBUG level to see all log messages
flog.threshold(DEBUG)
# Suppress log messages below WARN for logger 'quiet'
flog.threshold(WARN, name="quiet")

Appenders

An appender defines where output is directed. Typically only one appender is used per logger, but multiple can be assigned. The package provides the following appenders:

• appender.console
• appender.file
• appender.tee

To change the appenders assigned to a logger, use flog.appender():

# Change the 'quiet' logger to write to a file
flog.appender(appender.file('quiet.log'), 'quiet')
flog.warn("Goodbye, %s", "world", name='quiet')

You can create your own appender by defining a function that accepts a single character argument. It is up to you to define the behavior. For example, an appender that logs to a URL might look like the following.

url_appender.gen <- function(url) {
  conn <- url(url)
  function(line) {
    file.write()
  }
}

flog.format(“futile.matrix”, fn)

Layouts

A layout defines how a log message is printed. The default layout.simple prints log messages using the following format: LEVEL [datetime] Message

The layouts included in the package are: + layout.simple - Use a default format + layout.format - Provide a customizable format string + layout.tracearg - Dump a variable with its name

What’s New

• Function to wrap a try/catch with logging (ftry)
• Capture output for print statements (for more complex objects)
• New layout.tracearg

These binaries (installable software) and packages are in development.
They may not be fully stable and should be used with caution. We make no claims about them.
Health stats visible at Monitor.