You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Tweaking the level of the log of a succeeded process #157
The reasoning is that when you schedule a import task every hour, chances are that there are no file to import. However, there is still an "INFO" displayed even though the task technically did not do anything at all of value.
The idea would be to downgrade the log to DEBUG so that the presence or not of logs in the reports columns would mean something.
In my opinion if the client only wants to see the errors for his scheduled process then it means the command line in the cron (or other scheduler) should contains the --quiet (-q) flag: https://symfony.com/doc/current/console/verbosity.html
@VincentChalnot In this instance, the presence of an INFO log would mean that at least one file was treated by the task. This is why they asked us to remove this specific log because "info: 1" means 0 files treated et "info: 2" means 1 file treated.
The ProcessManager is not aware of what happens in each task right? Alltough I agree with you that this kind of message could be configured with a custom task according to the need of the process.
Activity
VincentChalnot commentedon Jan 15, 2025
In my opinion if the client only wants to see the errors for his scheduled process then it means the command line in the cron (or other scheduler) should contains the --quiet (-q) flag:
https://symfony.com/doc/current/console/verbosity.html
xaviermarchegay commentedon Jan 15, 2025
@VincentChalnot In this instance, the presence of an INFO log would mean that at least one file was treated by the task. This is why they asked us to remove this specific log because "info: 1" means 0 files treated et "info: 2" means 1 file treated.
VincentChalnot commentedon Jan 15, 2025
The ProcessManager is not aware of what happens in each task right? Alltough I agree with you that this kind of message could be configured with a custom task according to the need of the process.
xaviermarchegay commentedon Jan 15, 2025
One proposed solution would be to be able to configure the level of the messages of the bundle (info or debug).
VincentChalnot commentedon Jan 15, 2025
Seems like a good compromise but adds complexity. I would advise to deprecate this and force the message as debug for the next big release.
njoubert-cleverage commentedon Jan 15, 2025
On my mind, there are 2 differents informations :
njoubert-cleverage commentedon Oct 9, 2026
Without UI, this log is the only way to follow processes and must not be default set as debug.
I propose to add options under clever_age_process:
As ever, options may be override on process if needed.
success_level is used on Process {$history->getProcessCode()} succeed
failed_level is used on (new) Process {$history->getProcessCode()} failed
Merge pull request #257 from cleverage/157