Attributing object to log messages

All - Sorry for the delay. We never pursued this further as it appears to be benign failures (clients trying to connect via prohibited protocols, etc) that were always present but only now logged due to logging changes in newer versions. I asked support about getting additional information but the tech was unable to provide more info other than 'enable logging at debug level' as noted in K17045. I work in a risk-adverse environment so the issue was dropped as it is not attributed to a production issue.

The only other bit of information I found since this post was K5532, which outlines the logging levels available for certain event types. Not much help as it doesn't indicate what messages would be logged at each level so one cannot determine the level of logging that would need to be enabled. If I have time later I'll set up a test in my home lab to see if any level other than DEBUG provides any useful information. If I find something of interest I'll post here.

As of now, best information I have is to assess your current resource load then enable debug logging for SSL traffic per K17045.