By default Jaffa will internally log at various levels to the browser Console (if it is available):

• DEBUG: Disabled unless debuggingEnabled: true is set in configuration. Used during development, but not recommended unless you are hunting bugs.
• INFO: Information on significant events occurring during normal operation.
• WARN: Problems/errors (or just potential ones) that do not halt operation of Jaffa will be reported here.
• ERROR: Fatal errors that Jaffa (or just the utility you are using) will halt operations for are reported here, and also displayed in a dialog to the user.

Custom Logging

Providing custom logging is somewhat similar to what we've already seen on the 'Alerts' tab, we just provide a custom function in the functionLog configuration. Here is an example we use for this page to add a scolling log to this tab (below), although I've snipped out some of the less relevant stuff to avoid bloat. Perhaps it would be useful (along with debugging) on your site if the user is a super user?

var logging = null;
var debugLogging = function(type, message) {
    if (logging == null) {
        logging = $(".jaffa-logs");
    }
    var logLine = "<div class='log-row'>";
    logLine += "<span class='time'>" + now() + "</span>";
    logLine += "<span class='level'>" + type + "</span>";
    logLine += "<span class='message'>" + message + "</span>";
    logLine += "</div>";
    logging.prepend(logLine);
    // Send them to Jaffa's standard log as well, the null test
    //  avoids some issues in IE due to startup timing.
    if (jaffa != null) {
        jaffa.log(type, message);
    }
};

jaffa = jaffaFactory({
        debuggingEnabled: true,
        functionLog: debugLogging
    });

So with appropriate styling you can see the output in the fake 'window' below: