Attributing object to log messages
Since upgrading to v12.1.1 we're seeing SSL errors in /var/log/ltm. I believe this is due to behavior starting in v12.0 per SOL15292 ("Note: Beginning in 12.0.0, the BIG-IP system automatically logs SSL handshake failure information through standard logging"). However the log messages (samples below) do not indicate to which object they are attributed. Is there a way to determine which object throws these errors? Some (no shared ciphers) may not require further scrutiny but would like to trace some down to see if issue is something we need to pursue further.
Sample messages (timestamp and hostname removed; all following appear as 'warning' level):
tmm[22716]: 01260009:4: Connection error: ssl_cn_decrypt_fin_cb:2034: fin decryption failed (20)
tmm7[22717]: 01260009:4: Connection error: ssl_cn_decrypt_fin_cb:2034: fin decryption failed (20)
tmm5[22717]: 01260009:4: Connection error: hud_ssl_handler:1224: codec alert (20)
tmm3[22716]: 01260009:4: Connection error: ssl_passthru:4015: not SSL (40)
tmm4[22717]: 01260009:4: Connection error: ssl_passthru:4015: not SSL (40)
tmm4[22717]: 01260009:4: Connection error: ssl_hs_rxhello:7295: unsupported version (40)
tmm3[22716]: 01260009:4: Connection error: hud_ssl_handler:1224: codec alert (20)
My question may be better stated as: "Is there a document relating the log.ssl.level DB variable to the information logged to /var/log/ltm?" I see SOL17045 regarding some server-side logging that requires debugging and was hoping to find something documented rather than 'play' with log levels and observe results.