Skip to content
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

Informational messages are logged as errors #74

Closed
fubar opened this issue Mar 22, 2022 · 7 comments
Closed

Informational messages are logged as errors #74

fubar opened this issue Mar 22, 2022 · 7 comments

Comments

@fubar
Copy link

fubar commented Mar 22, 2022

Our logs show the below messages logged frequently and at error level:

I0322 06:00:50.813426       1 server.go:107] Servicing mount request for pod [...] in namespace default using service account [...] with region eu-west-1
I0322 06:00:51.010475       1 auth.go:123] Role ARN for [...] is arn:aws:iam::[...]

These are informational messages that should not be treated like errors.

@pierluigilenoci
Copy link

@fubar these are informational messages.
Why do you say they are treated like errors?

Keep in mind that Klog (the library used for logging) is affected by a fairly serious bug regarding error levels.
And I don't see any fixes on the horizon anytime soon.

Ref: kubernetes/klog#212

@fubar
Copy link
Author

fubar commented Mar 22, 2022

Interesting, that may as well be the cause. We're using a standard Datadog agent setup for logging, and all of those log events are logged at the error level in Datadog.

Does the AWS provider have any configuration options for logging?

@pierluigilenoci
Copy link

@fubar The CSI driver yes, the AWS provider no.

@fubar
Copy link
Author

fubar commented Mar 22, 2022

I'll try out the logFormatJSON option tomorrow, thanks!

@fubar
Copy link
Author

fubar commented Mar 23, 2022

I tried out the available options of the CSI driver, but they have no effect on the log level. Everything still gets logged as errors. Unfortunately, the only option we have is to not log anything the driver and provider are outputting.

@pierluigilenoci
Copy link

@fubar I quote myself.

Keep in mind that Klog (the library used for logging) is affected by a fairly serious bug regarding error levels. And I don't see any fixes on the horizon anytime soon.

Ref: kubernetes/klog#212

@simonmarty
Copy link
Contributor

We're waiting on the kubernetes team to fix the klog issue mentioned. Feel free to reopen when the upstream issue has been addressed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants