Lumberjack 1.0 had a concept of a unit of work id that could be used to tie log messages together. This has been replaced by tags. There is still an implementation of Lumberjack.unit_of_work, but it is just a wrapper on the tag implementation.

$ ./my_script Will end up in STDOUT(terminal) and /var/log/messages $ tail -n1 /var/log/messages Sep 23 15:54:03 wks056 my_script_tag[11644]: Will end up in STDOUT(terminal) and /var/log/messages

exec &> >(tee -a "$log_file")

exec &> >(tee -a "$log_file") echo "This will be logged to the file and to the screen" $log_file will contain the output of the script and any subprocesses, and the output will also be printed to the screen.

Pluggability uses the Loggability library. Just set the log level to 'debug' and it'll explain what's going on:

Almost always, I’m writing some kind of developer-script, and I want to write messages to both the terminal (to let the dev know what is going on), and to a log file (for future reference/audit).

I came up with a Delegator-like implementation of this that I called DelegatorToAll

I'll walk you through everything you need to know about logs, including what is log and how to use logs for data integration, real time processing, and system building.

Format clock summary as x:xx

Log the time a task is completed.

incidents are an unavoidable reality of working with distributed systems, no matter how reliable. A prompt alerting solution should be an integral part of the design,