-
Notifications
You must be signed in to change notification settings - Fork 332
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
Add logging verbosity to configuring OVN logs #3166
Conversation
/lgtm |
/lgtm @trozet ? |
When updating a large number of address_set, logs get flooded with "Configuring OVN" which cannot be reduced. Also klog shows up in the profiling data as a source of CPU consumption of ovnkube-master. We make it configurable and assign it a verbosity of 5. Default on OpenShift is 4, however this log is redundant with the "transacting operations" that is already logged with level 4. Signed-off-by: François Rigault <frigo@amadeus.com>
Sharing the result now, with sample logs:
before this commit, with loglevel=3, the Configuring OVN was still logged
|
superseded by pr above |
We need to get this PR in and its separate from other refactors happening. @freedge : hope this is ok with you, I am not sure why you closed this PR. |
I thought you were thinking of a more thorough redesign, and didn't want to add extra burden on you. |
When updating a large number of address_set, logs get flooded with "Configuring OVN" which cannot be reduced.
Also klog shows up in the profiling data as a source of CPU consumption of ovnkube-master.
We make it configurable and assign it a verbosity of 4 which is default on OpenShift.
Signed-off-by: François Rigault frigo@amadeus.com