Description
Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Since public network orchestrators need to expose certain ports to the public internet, it is likely that they will be the target of TCP probes and scanners checking for remote port connectivity [1]. The net/http package (used to create the orchestrator's HTTP(S) server) by default will use the log package's standard logger if any errors are encountered during an inbound request. As a result, if someone ran a TCP probe like this:
[1] See this article for a good overview for this and other considerations when running a Go based server on the public internet.
nc -cz localhost 8935
The following log would appear for the orchestrator that has an HTTP(S) server at localhost:8935
2020/10/27 09:34:33 http: TLS handshake error from [::1]:49797: EOF
These logs can very quickly fill up an orchestrator's logs.
Describe the solution you'd like
A clear and concise description of what you want to happen.
Suppress the error logs from net/http at least with the default logging level used for the orchestrator. It might make sense to still log those errors, but only if the logging level is set to VERBOSE. It should be possible to set a custom logger for Server.ErrorLog that catches and handles errors from net/http.