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
Currently kedro logs to info.log and error.log files by default as well as to the console. Do some sort of user poll to find out how many people use the info.log and error.log files or whether we should just log to the console.
antonymilne
changed the title
Remove the file-based logging handlers by default. also needed for databricks? do a poll
User research to see if we should remove the file-based logging handlers
Apr 22, 2022
antonymilne
changed the title
User research to see if we should remove the file-based logging handlers
User research + implement removing the file-based logging handlers
Apr 22, 2022
antonymilne
changed the title
User research + implement removing the file-based logging handlers
User research to see if we should remove the file-based logging handlers
Apr 22, 2022
I use info.log to log verbose information regarding the execution of an algorithm that I run in a node. If the output of the algorithm shows unexpected results, I can look in info.log to see what could have caused this unexpected result.
I use the logs in the directory mainly when running inside the docker container created with the kedro-docker plugin.
When developing I mostly look at the console output even though it's useful to have a running history of previous executions even when developing
Conclusion
People do use the logs files. Let's leave them there.
Currently kedro logs to info.log and error.log files by default as well as to the console. Do some sort of user poll to find out how many people use the info.log and error.log files or whether we should just log to the console.
For context, see @noklam's comment here and following discussion: #1461 (comment).
The text was updated successfully, but these errors were encountered: