https://kedro.org/ logo
#questions
Title
# questions
l

Lahari Revuri

03/27/2024, 2:15 PM
Hi all, I recently migrated from 0.18.13 to 0.19.3 and have set
KEDRO_LOGGING_CONFIG
to use a custom logging file. However, one thing I can't seem to do anymore is use a resolver in
logging.yml
? E.g.
logs/${runtime_params:example}.log
does not work. I did add logging file patterns to
CONFIG_LOADER_ARGS
in
settings.py
but not sure what else to try here.
Copy code
CONFIG_LOADER_ARGS = {
   "config_patterns": {
     "logging": [logging*", "logging*/**", "**/logging*"],
   }
 }
s

Sajid Alam

03/27/2024, 4:13 PM
Hey @Lahari Revuri, following 0.19.x, I don't think that resolvers within the
logging.yml
file is directly supported anymore either through the
KEDRO_LOGGING_CONFIG
or
logging.yml
itself. Following this discussion it was decided that kedro would move away from project-specific
logging.yml
files towards a more simplified approach where logging config is set through the
KEDRO_LOGGING_CONFIG
. This had had the indirect affect on the use of resolvers.
l

Lahari Revuri

03/27/2024, 5:57 PM
Thanks for linking the discussion - I can see the reasoning for this change. Is the right way to think about this that the logging.yml is picked up before other steps happen and doesn't "go through" the config loader at all?
šŸ‘šŸ¼ 1
n

Nok Lam Chan

03/28/2024, 10:58 AM
Exactly, logging will happened before everything, so it has to be earlier than ConfigLoader is being created. There are two related discussion happening, if you'd like to chime in. ā€¢ https://github.com/kedro-org/kedro/issues/3446 ā€¢ https://github.com/kedro-org/kedro/issues/3591
šŸ‘ 1