Huge increase in default log verbosity with AGIC 1.7.5

[bondido]

After updating AGIC on AKS from version 1.7.4 to 1.7.5 we've noticed huge spike in log size from ingress-azure container. As we are sending AKS container logs to Log Analytics, the change also implied increased costs.

I've found the commit: https://github.com/Azure/application-gateway-kubernetes-ingress/commit/91c71a1f70c666886379c36ca0a96d531b3b224c that moved some logs from verbosity level 5 to 3.

As I can see, '3' is default value if we don't override it with helm chart installation variables.

What's more. I think the docs are wrongly stating that the default verbosity level is '1'. https://azure.github.io/application-gateway-kubernetes-ingress/logging-levels/

To Reproduce Update AGIC version 1.7.4 -> 1.7.5 with default value of verbosityLevel variable

[nshakhat]

Experiencing the same. The most annoying part is the fact that config file is being logged, e.g. https://github.com/Azure/application-gateway-kubernetes-ingress/blob/master/pkg/controller/mutate_app_gateway.go#L70 . Observability backends do not manage it well, which creates a lot of false-errors. Of course it can be fixed, but quite a lot of efforts is required. Unfortunately, there is also no simple way to change the verbosity level, only a manual change like:

kubectl set env deployment/ingress-appgw-deployment -n kube-system APPGW_VERBOSITY_LEVEL=1

Maybe it can be helpful for someone, so leaving it here.