[X] ... the documentation does not mention anything about my problem
[X] ... there are no open or closed issues that are related to my problem
Description
When DIUN skips a notification (e.g. on first check) the related log entry is shown only on a debug log level, which may be confusing. In my case I was trying to debug notifications (specifically Telegram), while they are completely functional. Switching to debug logs made me observe the true reason on why the notification was not sent.
Expected behaviour
Assign the "Skipping notification" log to the info level
Actual behaviour
The "Skipping notification" is only shown at debug level
diun | Tue, 18 Jun 2024 18:40:17 CEST INF New image found image=lscr.io/linuxserver/mariadb:latest provider=docker
diun | Tue, 18 Jun 2024 18:40:17 CEST DBG Manifest saved to database image=lscr.io/linuxserver/mariadb:latest provider=docker
diun | Tue, 18 Jun 2024 18:40:17 CEST DBG Skipping notification (first check) image=lscr.io/linuxserver/mariadb:latest provider=docker
Support guidelines
I've found a bug and checked that ...
Description
When DIUN skips a notification (e.g. on first check) the related log entry is shown only on a
debug
log level, which may be confusing. In my case I was trying to debug notifications (specifically Telegram), while they are completely functional. Switching todebug
logs made me observe the true reason on why the notification was not sent.Expected behaviour
Assign the "Skipping notification" log to the info level
Actual behaviour
The "Skipping notification" is only shown at debug level
Steps to reproduce
docker compose up -d && docker compose logs -f
Diun version
4.28.0
Docker info
Docker Compose config
No response
Logs
Additional info
No response