@fnegri I suspect that in most cases the additional manual logging is done because the START/END messages were not logged. Now that they are I guess that most of those additional logs calls can be dropped by just implementing the runtime_description() property in most cookbooks that will log the same information in the START/END messages. But correct me if this assumption is wrong.

@Volans yes I think maybe 80% of the messages could be replaced by a runtime_description, but we will still have situations where we want to log multiple "steps" in a cookbook, something like:

• START
• doing step 1
• doing step 2
• END

It would be trivial to switch our current SALLogger calls for those situations to a call to sal_logger (the one provided by Spicerack). We could even do an easy search/replace of all the existing calls to SALLogger, and leave the migration to runtime_description for later.

The real blocker is that Spicerack's sal_logger doesn't work if you run cookbooks from a laptop... which is the current status quo. If we successfully move all our cookbook users to running them from cloudcumin, then we can remove our custom SALLogger and use sal_logger for everything.

Whether we can ask everyone to use cloudcumins will also depend on T343330.