-
Notifications
You must be signed in to change notification settings - Fork 300
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Debug logs being written to stderr #320
Comments
@marty2bell You can disable debug logs by setting |
@aramase Thanks for the tip on disabling debug |
Hey @aramase Any thoughts on how to address this as it's causing quite a bit of noise in our production environment? Doesn't look like logrus is going to change for new features...... |
@marty2bell I think the right way to fix the problem is to switch to use |
/close (With switch to |
@aramase: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
What steps did you take and what happened:
[A clear and concise description of what the bug is.]
These logs from the secret store image seem to be written to sdterr which causes alerts in our monitoring solution.
time="2020-09-16T19:30:12Z" level=debug msg="GRPC request: "
time="2020-09-16T19:30:12Z" level=debug msg="GRPC response: ready:<value:true > "
time="2020-09-16T19:30:14Z" level=debug msg="GRPC call: /csi.v1.Node/NodeGetCapabilities"
What did you expect to happen:
Write debug logs to sdtout.
Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]
Also, is there a mechanism to turn off debug logs, tune the logging level to info for example?
Which provider are you using:
[e.g. Azure Key Vault, HashiCorp Vault, etc. Have you checked out the provider's repo for more help?]
We are using this driver on AKS with Azure Key Vault
Environment:
kubectl version
): 1.18.6The text was updated successfully, but these errors were encountered: