Has the behaviour of `PREFECT LOGGING EXTRA LOGGERS` changed

Question

Has the behaviour of `PREFECT LOGGING EXTRA LOGGERS` changed from `2 6 7` to `2 6 9` at all I was previously using it successfully in combination with `DaskTaskExecutor` and `dask jobqueue SLURMCluster` to capture logs from another package It seems though with an updated to `2 6 8` or `2 6 9` I have lost this ability I do see the logs being printed to my slurm output files and I do see it is formatted in the `prefect` style but I am not seeing these logs being submitted through to my self hosted Orion server as presented by the web UI Any ideas

Tim Galvin · Answer

Ahhh I see that there is now a `logging yml` capability I suppose this is now changing the behaviour of the `PREFECT LOGGING EXTRA LOGGERS` variable I was using Can anyone confirm

Tim Galvin · Answer

Lets say in an earlier version of `prefect` I would use `PREFECT LOGGING EXTRA LOGGERS= mymodule ` what would be the proper way of using the new interface to capture these logs I see in the docs I can do something like ```PREFECT LOGGING PATH TO KEY =value``` Is there a way of specifying these extra modules Would it be something like ```export PREFECT LOGGING LOGGERS MYMODULE LEVEL=INFO export PREFECT LOGGING LOGGER MYMODULE HANDLERS= orion console ```

Tim Galvin · Answer

Actually now I am not sure Reading the code in `prefect src logging configuration py` seems to have the `PREFECT LOGGING EXTRA LOGGERS` logic in there and as far as I can tell from the `logging yml` file these extra modules should be logged to both the `orion` and `console` handlers But it seems like mine are only recorded to the console

Mason Menges · Answer

~Hey Tim the only thing I know of that was included in 2 6 9 was Dask Worker logs should be getting surfaced on the task run logs within prefect now if have a Minimum Reproducible example of the code setup you re running it might be worth opening a bug on the github repo ~ Missed the new message you posted you can ignore this haha sweat smile