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

fix: mute noisy log messages by default #10

Merged
merged 1 commit into from
Feb 14, 2024
Merged

Conversation

diafour
Copy link
Member

@diafour diafour commented Feb 13, 2024

Description

  • Use level 4 for trace messages like UpdateMetadata and UpdateStatus.
  • Add messages to distinguish reconcile steps.
  • Add message with reconcile result to see if requeue was requested.

Why do we need it, and what problem does it solve?

UpdateMetadata and UpdateStatus are too noisy for default debug log level.

What is the expected result?

Developer should change VERBOSITY to 4 to see more detailed huge logs.

Checklist

  • The code is covered by unit tests.
  • e2e tests passed.
  • Documentation updated according to the changes.
  • Changes were tested in the Kubernetes cluster manually.

- Use level 4 for trace messages like UpdateMetadata and UpdateStatus.
- Add messages to distinguish reconcile steps.
- Add message with reconcile result to see if requeue was requested.

Signed-off-by: Ivan Mikheykin <[email protected]>
@diafour diafour self-assigned this Feb 13, 2024
@diafour diafour merged commit 03704aa into main Feb 14, 2024
8 checks passed
@diafour diafour deleted the fix/noisy_log_messages branch May 28, 2024 10:25
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

Successfully merging this pull request may close these issues.

2 participants