-
Notifications
You must be signed in to change notification settings - Fork 306
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
Calico logging is set to INFO #925
Comments
@feiskyer FYI |
The INFO level would help for understanding what calico is working and troubleshooting calico issues if there's something wrong. Decrease the log level would lose such flexibility. @ams0 How much disk space have you observed? |
related to Azure/aks-engine#2111 In our k8s clusters (aks-engine), calico generates around 30% of the logs in the system !! |
This might be better for a feature request, but the ability to change the log level would be nice |
This issue has been automatically marked as stale because it has not had any activity for 60 days. It will be closed if no further activity occurs within 15 days of this comment. |
Just in case it's useful, this is the fix in aks-engine Azure/aks-engine#3396, making its log level configurable. |
Action required from @Azure/aks-pm |
Thanks for your feedback. |
@TomGeske I'd reopen it. For us is still an issue. Around 30% of our logs are generated by calico, so we have ended up discarding ALL its logs in the fluent-bit daemonset we use to gather our platform's logs. |
+@jluk for visibility |
This issue has been automatically marked as stale because it has not had any activity for 60 days. It will be closed if no further activity occurs within 15 days of this comment. |
This issue will now be closed because it hasn't had any activity for 15 days after stale. ams0 feel free to comment again on the next 7 days to reopen or open a new issue after that time if you still have a question/issue or suggestion. |
What happened:
Deploying calico in AKS the
calico-node
pods are set to log up to severity "INFO".What you expected to happen:
A lower logging severity to avoid unnecessary waste of disk space.
How to reproduce it (as minimally and precisely as possible):
Currently only available on up to 1.11 clusters because of #905
The text was updated successfully, but these errors were encountered: