Backport of [API Gateway] Turn down controller log levels into release/1.15.x #16352
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
hc-github-team-consul-core
force-pushed
the
backport/api-gateway-trace-logs/strongly-enhanced-cow
branch
from
84fc232
to
c1d9d80
Compare
github-team-consul-core-pr-approver
approved these changes
Feb 22, 2023
hc-github-team-consul-core
deleted the
backport/api-gateway-trace-logs/strongly-enhanced-cow
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Backport
This PR is auto-generated from #16348 to be assessed for backporting due to the inclusion of the label backport/1.15.
The below text is copied from the body of the original PR.
Description
This turns down all of our controller debug logs to trace logs to avoid too much spam. Additionally, all controller
Errorlogs are moved toWarnlevel since:Errorwould be logged for things like a failed reconciliation due to a CAS mismatch, which could just occur with high volumes of writes to a corresponding ConfigEntryAccordingly, it's probably more of a "warning" level than something we'd want to alert the user on at the "error" level.
PR Checklist
Overview of commits