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

Make "info" logs less verbose #1104

Open
burkart opened this issue Feb 25, 2024 · 0 comments
Open

Make "info" logs less verbose #1104

burkart opened this issue Feb 25, 2024 · 0 comments

Comments

@burkart
Copy link

burkart commented Feb 25, 2024

Description

Using the default LOG_LEVEL "info", the log contains 4 lines per (Cron) execution even though nothing out of the ordinary happened:

[timestamp] INF Cron triggered
[timestamp] INF Found 123 image(s) to analyze provider=docker
[timestamp] INF Jobs completed added=0 failed=0 skipped=0 unchanged=123 updated=0
[timestamp] INF Next run in 6 hours 2 seconds ([timestamp])

Setting the LOG_LEVEL to "warn" is undesirable because that would disable "info" output for updated images:

[timestamp] INF Cron triggered
[timestamp] INF Found 123 image(s) to analyze provider=docker
[timestamp] INF Image update found image=docker.io/hello-world:latest provider=docker
[timestamp] INF Jobs completed added=0 failed=0 skipped=0 unchanged=122 updated=1
[timestamp] INF Next run in 5 hours 59 minutes ([timestamp])

Suggestion:

Demote outputs from "info" to "debug" (or introduce intermediate level "verbose") that contain little valuable information:

  • "Cron triggered"
  • "Found [n] image(s) to analyze"
  • "Jobs completed" where added, failed, updated, and possibly skipped are all 0
  • "Next run in"
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant