From a debugger's point of view, one of the things I really like about a particular piece of vendor software we use at work is its ability to change logging levels of different components of itself.

For instance, you could have the general logging verbosity set to "info" but have specific portions of the system like "accounts" or "roles" log at the level of "debug".

This makes it real flexible. It also makes it nice when it comes to debugging. Often savory can emit a lot of messages when it is set to global level debugging. This makes it hard to see a problem fly by. You can Splunk the logs to find errors easier, but there is still a lot of logging that takes place.

Well, as of today, savory includes class level logging in addition to global level logging.

This makes it possible to debug a particular class, or set of classes, without enabling full debug on the system.