Logging¶

Logging Methods¶

The log_critical, log_warning, log_detail, and log_deprecated methods are used to log custom data to the Lasso internal error logs with a defined Lasso error level of “Critical”, “Warning”, “Detail”, or “Deprecated”, respectively.

log_critical(...)¶

Logs to Lasso’s internal error logs with an error level assignment of “Critical”. Requires the text to be logged as a parameter. Logging options for this error level are set in Lasso Server Admin.

log_warning(...)¶

Logs to Lasso’s internal error logs with an error level assignment of “Warning”. Requires the text to be logged as a parameter. Logging options for this error level are set in Lasso Server Admin.

log_detail(...)¶

Logs to Lasso’s internal error logs with an error level assignment of “Detail”. Requires the text to be logged as a parameter. Logging options for this error level are set in Lasso Server Admin.

log_deprecated(...)¶

Logs to Lasso’s internal error logs with an error level assignment of “Deprecated”. Requires the text to be logged as a parameter. Logging options for this error level are set in Lasso Server Admin.

log_always(...)¶

Logs to Lasso’s console. This error level cannot be routed, and is always sent to Lasso’s console.

handle(error_code == error_code_divideByZero) => {
   log_warning('A mathematical error occurred while processing this page')
}

// => [2013-03-23 16:59:41] A mathematical error occurred while processing this page

Logging to Files¶

In addition to using the built-in log level routing system, it is sometimes desirable to create a separate log file specific to a custom solution. The log method can write text messages out to a log file.

log(path)¶

When executed, the results of the auto-collection from the log method’s capture block is appended to a specified text file. The log method can write to any text file that is accessible from Lasso. The capture block must be an auto-collect block as the collected data from the capture block will be included in the appended data. If you don’t use an auto-collect block then no data will be appended to the log file.

The following example outputs a single line containing the date and time with a return at the end to the file specified. The methods are shown first with a Windows path, then with an OS X or Linux path.

log('C://Logs/LassoLog.txt') => {^
   date->format('%Q %T')
   '\r\n'
^}

log('//Logs/LassoLog.txt') => {^
   date->format('%Q %T')
   '\n'
^}

The path to the directory where the log will be stored should be specified according to the same rules as those for the file methods. See the section Paths in the File System chapter for full details about relative, absolute, and fully qualified paths on OS X, Linux, and Windows.

log('//tmp/foo.bar') => {^
   date->format('%Q %T') +
   ' ' + web_request->remoteAddr +
   ' ' + (web_request->isHttps ? 'https://' | 'http://') +
   web_request->httpHost +
   web_request->requestUri +
   ' ' + web_request->postParams + '\n'
^}

local(cur_date) = date->format('%Q')
log('//Logs/' + #cur_date + '.txt') => {^
   date->format('%Q %T')
^}

Log Routing¶

Log preferences can be viewed or changed in the “Log Book” section of Lasso Server Admin. Use of the log_setDestination method is only necessary to change the log settings programmatically.

log_setDestination(level::integer, dest1::integer=?, dest2::integer=?, dest3::integer=?)¶

The first parameter specifies a log message level. Subsequent parameters specify the destination to which that level of messages should be logged. Both the log level and any destinations are specified with integer values. It is preferred that you use the convenience methods described below as parameters rather than using literal integer values.

log_level_critical()¶

Returns the integer value for specifying the “Critical” message level in the log_setDestination method. Using this method will help future-proof your code.

log_level_warning()¶

Returns the integer value for specifying the “Warning” message level in the log_setDestination method. Using this method will help future-proof your code.

log_level_detail()¶

Returns the integer value for specifying the “Detail” message level in the log_setDestination method. Using this method will help future-proof your code.

log_level_deprecated()¶

Returns the integer value for specifying the “Deprecated” message level in the log_setDestination method. Using this method will help future-proof your code.

log_destination_console()¶

Returns the integer value for specifying the “Console” destination in the log_setDestination method. Using this method will help future-proof your code.

log_destination_file()¶

Returns the integer value for specifying the “File” destination in the log_setDestination method. Using this method will help future-proof your code.

log_destination_database()¶

Returns the integer value for specifying the “Database” destination in the log_setDestination method. Using this method will help future-proof your code.

log_setDestination(
   log_level_detail,
   log_destination_database,
   log_destination_console
)

log_setDestination(
   log_level_critical,
   log_destination_console,
   log_destination_database,
   log_destination_file
)
log_setDestination(log_level_warning,    log_destination_console)
log_setDestination(log_level_detail,     log_destination_console)
log_setDestination(log_level_deprecated, log_destination_console)