-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
KEDA Metrics API Server not honoring Loglevels #2316
Comments
Could you please confirm the same problem on 2.5.0? |
Yes, it's still present in 2.5.0 I did a little bit of digging and the traced line seems to come from the kubernetes-apiserver. I haven't found the section where this function is executed in Keda, but it seems to return the trace on v(0).Info level. Line 167 in 4a1e358
Maybe that helps somehow |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 7 days if no further activity occurs. Thank you for your contributions. |
This issue has been automatically closed due to inactivity. |
this is still an issue, even in keda 2.6.1. |
Still on 2.7.1 |
I have been checking klog docs and there they tell that we MUST call |
This might be the case, hard to tell 🤷♂️ Have you been able to test your propsed fix? To see if there aren't these messages anymore? |
I have checked e2e test output to be sure, but let me deploy it into a testing cluster for some days, just to double-check 😄 |
Report
What is happening?
Kede Matrics Api Server is spamming trace logs, even though logging is set to v=0
Config
Logs
Expected Behavior
When setting loglevel to 0, only level 0 and below should be logged
( as per log documentation)
Actual Behavior
Traces are logged
Steps to Reproduce the Problem
Logs from KEDA operator
KEDA Version
2.4.0
Kubernetes Version
1.20
Platform
Microsoft Azure
Scaler Details
Prometheus Scaler / Metrics API Scaler
Anything else?
No response
The text was updated successfully, but these errors were encountered: