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 with the ned DAG and all, there is a lot of logging and sometimes it makes it difficult to know what is from where, especially if debug is enabled.
I propose some kind of ID logged along the lines, that refers to that step only so it can easily be tracked at a glance and even grepped easily to only get the logs for that ID. Kind of what its done on threaded apps where you want to track just one query along the system.
Not sure if the DAG already sets a unique identifier per task that could be used? @mudler
The text was updated successfully, but these errors were encountered:
Currently with the ned DAG and all, there is a lot of logging and sometimes it makes it difficult to know what is from where, especially if debug is enabled.
I propose some kind of ID logged along the lines, that refers to that step only so it can easily be tracked at a glance and even grepped easily to only get the logs for that ID. Kind of what its done on threaded apps where you want to track just one query along the system.
Not sure if the DAG already sets a unique identifier per task that could be used? @mudler
The text was updated successfully, but these errors were encountered: