As a Confluence administrator, it would be helpful to have improved logging round Synchrony:

• In a scenario where Confluence Data Center is managing Synchrony, and the internal proxy is not enabled, Sychrony traffic will be directed through /synchrony first, and failing that, will try /synchrony-proxy and finally confluence-context-path/synchrony-proxy. It wold be useful to know when/why Confluence uses the alternate paths to reach Synchrony.
• Similarly, logging around failed websocket upgrades could help administrators understand why the failover to XHR occurs.
• There's a lot of noise in the Synchrony logs, and so the ability to filter out the noise would be useful. Unfortunately, changing the level of Synchrony logging from DEBUG to WARN (for example) stops all logging, so it can't be done that way.