Change ForwardAuth error log level from DEBUG to ERROR #12324
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this PR do?
When the ForwardAuth middleware fails to reach the authentication server, it returns a 500 error but logs at DEBUG level, making it difficult to diagnose issues in production without enabling debug logging.
This change promotes the error log to ERROR level for better observability.
Motivation
As reported in #12234, when the ForwardAuth middleware cannot reach the auth server (e.g., DNS resolution failure, network issues), users receive 500 errors with no indication in logs unless DEBUG level is enabled. This makes troubleshooting production issues very difficult.
Example log before this change:
Example log after this change:
Changes
Debug()toError()inpkg/middlewares/auth/forward.goline 198Fixes #12234