community 
Which logging method?
There are two methods for logging from drivers - cloudshell.networking.devices.driver_helper.get_logger_with_thread_id() and cloudshell.core.logger.qs_logger.get_qs_logger(). The Dev Guide recommends get_qs_logger(), but I see both methods used in Quali’s drivers. Which is the recommended method and why?
Hi @jim.pfleger.vz,
The qs_logger is a good solution for most cases, it's thread-safe and lock-safe and is using the python's logging package.
In some cases, like with the drivers you saw, we use another wrapper, that basically uses the get_qs_logger and allows adding the thread name to the log information.
This is useful mostly for drivers that support concurrent commands (the option under Resource Manager/Families/Model/Drivers). In such drivers, it will be hard to follow the log file if several commands are executed simultaneously, so we add the thread name to each line in the log.
So instead of seeing such lines in the log:
2017-01-31 16:44:39,947 [INFO]: vCenterShell.VMware_vCenter command_wrapper - get_py_service_connection Creating a new connection.
You'll see this (note the Thread-5):
2017-10-11 12:49:42,325 [INFO]: QS.cisco_ios_router1.Thread-5 driver - get_inventory Autoload started
So, if you're not going to support concurrent commands, it's fine to use the get_qs_logger.
Yaniv
