change log level of missing proxy protocol headers

[nwsparks]

when traffic is received by kong that is missing the proxy protocol headers, it generates an error level event in the logs. this can be extremely spammy and im not sure that an error level event is warranted for this. if it were changed to a lower log level, then the log level could be changed to suppress this.

the specific issue im running into is aws nlb sending health checks to cilium which then forwards them to kong.

• nlb tcp health checks don't include the headers so they cause this error in the kong logs
• http health checks go to ciliums health endpoint which doesn't support ppv2
• the kong helm chart doesn't support exposing the kong status endpoint so that it can be used instead of the above two health checks.

so assuming my understanding of everything is correct, the only option is to use the tcp health checks which keep everything online, but they spam the log with this log event

[error] 1407#0: *2506 broken header: "" while reading PROXY protocol