z/OS Connect Service Provider Logging Control

As of Service Provider com.rs.dv.zosconnect.provider.feature_1.0.0.201904081546.esa (Notice the Date/Time Stamp is also in the name now) logging can now be controlled from from a Server.xml Parm.   The default traceLevel is now INFO.  With INFO you get Informational, Warnings, Errors, and Fatal messages written. 
It will also log messages for each service refreshed and give you a count of the total number of services refreshed when a refresh is run.
<usr_dvsService id="dvsService" ...  traceLevel="INFO" />

Successful service runs will NOT generate any messages.  You still can get logging on these successful runs in the DVM Trace Browse by setting the ZCONNECTTRLEV Parm.
lev  meaning...                  
---  ----------                  
 0   No tracing                  
 1   Trace path start/stop       
 2   1 + trace request begin/end 
 3   2 + trace request info      
 4   3 + trace i/o buffers       

Note: Service Providers prior to this had DEBUG as the default level which would write multiple lines to the STDOUT of the zcEE Server Instance for each successful service ran.
<usr_dvsService id="dvsService" ...  traceLevel="DEBUG" />

The levels come from Log4j.   

Level	Description
OFF	The highest possible rank and is intended to turn off logging.
FATAL	Severe errors that cause premature termination. Expect these to be immediately visible on a status console.
ERROR	Other runtime errors or unexpected conditions. Expect these to be immediately visible on a status console.
WARN	Use of deprecated APIs, poor use of API, 'almost' errors, other runtime situations that are undesirable or unexpected, but not necessarily "wrong". Expect these to be immediately visible on a status console.
INFO	Interesting runtime events (startup/shutdown). Expect these to be immediately visible on a console, so be conservative and keep to a minimum.
DEBUG	Detailed information on the flow through the system. Expect these to be written to logs only. Generally speaking, most lines logged by your application should be written as DEBUG.
TRACE	Most detailed information. Expect these to be written to logs only. Since version 1.2.12.[11]

In reality, the Service Provider only logs DEBUG, INFO, and ERROR messages.  But, in the future, it?s always possible that we would add messages at other trace levels.