Comment 38 for bug 1492140

Well, I was thinking maybe we could do something similar to this patch, where we changed the default log level of the oslo.privsep daemon to log at INFO instead of its default DEBUG, in nova:

https://review.opendev.org/#/c/586643/2/nova/config.py

So I was thinking for websockify we could do similar and set the level to WARN instead of INFO.

Doing that isn't ideal for debugging though because we'd miss logs about whether the proxy is running with TLS support, which I have used for troubleshooting before in the past, example:

Dec 05 11:21:47.775193 ubuntu-bionic-inap-mtl01-0013232262 nova-novncproxy[24376]: INFO nova.console.websocketproxy [-] WebSocket server settings:
Dec 05 11:21:47.775615 ubuntu-bionic-inap-mtl01-0013232262 nova-novncproxy[24376]: INFO nova.console.websocketproxy [-] - Listen on 0.0.0.0:6080
Dec 05 11:21:47.776478 ubuntu-bionic-inap-mtl01-0013232262 nova-novncproxy[24376]: INFO nova.console.websocketproxy [-] - Web server (no directory listings). Web root: /usr/share/novnc
Dec 05 11:21:47.776647 ubuntu-bionic-inap-mtl01-0013232262 nova-novncproxy[24376]: INFO nova.console.websocketproxy [-] - SSL/TLS support
Dec 05 11:21:47.777505 ubuntu-bionic-inap-mtl01-0013232262 nova-novncproxy[24376]: INFO nova.console.websocketproxy [-] - proxying from 0.0.0.0:6080 to None:None
...
Dec 05 11:47:49.788915 ubuntu-bionic-inap-mtl01-0013232262 nova-novncproxy[24376]: INFO nova.console.rfb.authvencrypt [None req-d3d9db7c-89fe-44f2-95a6-ef3357a25f1b None None] VeNCrypt security handshake accepted
Dec 05 11:47:49.789176 ubuntu-bionic-inap-mtl01-0013232262 nova-novncproxy[24376]: INFO nova.console.securityproxy.rfb [None req-d3d9db7c-89fe-44f2-95a6-ef3357a25f1b None None] Finished security handshake, resuming normal proxy mode using secured socket

I'll look into the logging issue again to see if I can possibly find another way around.