@huntc wrote:
I feel that Akka HTTP is quite chatty when it comes to logging and want to share my production-based experience to see if we could/should make it less so.
I’ve been running Akka HTTP in production now for well over a year. My HTTP endpoints are exposed to the outside world and don’t have a proxy in front. I realise that Akka HTTP is a fairly low-level abstraction, and perhaps I should have a hardened proxy, but as this particular service only has one instance right now, I wanted to keep the infrastructure as simple as possible.
Here are some of the many, many messages that are filling up my logs:
WARN ActorSystemImpl - Illegal request, responding with status '400 Bad Request': Illegal HTTP message startWARN ActorSystemImpl - Illegal request, responding with status '400 Bad Request': Unsupported HTTP method: The HTTP method started with 0x16 rather than any known HTTP method. Perhaps this was an HTTPS request sent to an HTTP endpoint?WARN ActorSystemImpl - Illegal request, responding with status '400 Bad Request': Unsupported HTTP method: HTTP method too long (started with '238ll|'|'|SGFjS'). Increase `akka.http.server.parsing.max-method-length` to support HTTP methods with more characters.WARN ActorSystemImpl - Illegal request, responding with status '400 Bad Request': Cannot establish effective URI of request to `/`, request has a relative URI and is missing a `Host` header: consider setting `akka.http.server.default-host-header`That’s just a quick sample. Frankly, I don’t care about any of these as an operator. Would there be an appetite to review all log messages of Akka HTTP and relegate most to DEBUG?
Posts: 1
Participants: 1