Logging issues

[martin-volf]

There are several interrelated issues with logging, some of them reaching into the gnmi-tools project:

• logging is not really configurable, only its level can be changed via a CLI option;
• the way how confd_gnmi_* loggers are disabled/enabled is far from standard, hence likely to cause confusion or bugs
• confd_gnmi_client and confd_gnmi_rpc loggers are used within one module, maybe they can be unified somewhat
• SubscriptionRequest instances sent to the stream and SubscriptionResponse instances received from the server are not logged at all, because they do not go through the API.

See also ConfD-Developer/ConfD-Demos#106 (review).

[jomiklos]

logging is not really configurable, only its level can be changed via a CLI option;

this should be taken care of by simply setting the robot run trace level, - this internally sets the default logging level for all loggers in python code i believe...

confd_gnmi_client and confd_gnmi_rpc loggers are used within one module, maybe they can be unified somewhat

i disagree here, at least partially -> there's lot of information in "client" logger that is completely uninteresting out of client debugging bounds i believe (e.g. names of procedures etc.), while "rpc" logger tracks potentially the only/very interesting details for non-programmer user - of actual RPC messages being dispatched between client/server.