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

Proposal: Reduce the amount of INFO Logs #53

Open
alxndr13 opened this issue Aug 2, 2023 · 2 comments · May be fixed by #214
Open

Proposal: Reduce the amount of INFO Logs #53

alxndr13 opened this issue Aug 2, 2023 · 2 comments · May be fixed by #214

Comments

@alxndr13
Copy link
Contributor

alxndr13 commented Aug 2, 2023

Proposal / Comment from an inovex colleague:

We could drastically reduce the amount of logs for each event and set them to loglevel debug.

Instead of logging each event in info we could summarize the creation, deletion, update count at the end of the sync process.

@MichaelEischer
Copy link
Collaborator

MichaelEischer commented Aug 2, 2023

Just marking all log output for events that are already sync as debug would also reduce the log output significantly.

@alxndr13
Copy link
Contributor Author

alxndr13 commented Aug 4, 2023

I just looked at the code and thought we could still log (create / update and delete events) in INFO but put all the skipped steps and "event in sync" messages to DEBUG. In this case, the user would only get logs for events where changes happen. (First runs would still be verbose)

timonegk added a commit that referenced this issue Dec 19, 2024
@timonegk timonegk linked a pull request Dec 19, 2024 that will close this issue
timonegk added a commit that referenced this issue Jan 13, 2025
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 a pull request may close this issue.

2 participants