❓ Kedro logging question: We have a fastapi application where we define a AzureLogHandler at the beginning:

logger = CorrelatedLogger.get_logger()

    log_handler = AzureLogHandler(connection_string=connection_string)
    logger.addHandler(log_handler)

    logger.setLevel(logging.INFO)

We then create a kedro session to get the catalog and load some datasets (we have to use a session because of certain hooks to allow us to load datasets). However, the creation of the session and loading of the associated

logging.yaml

completely breaks the logging config of the CorrelatedLogger … If I add the same logging config as in the snippet above after the kedro session was closed again. It all works. I did not expect the loading of the kedro project logging config to break any existing logging handlers or setup. Anyone got an idea?

There is a line in the logging file that disable existing logger IRRC

If I add

incremental: True

I get the following

File "/anaconda/envs/test/lib/python3.9/logging/config.py", line 508, in configure
    raise ValueError('No handler found with '
ValueError: No handler found with name 'console'

@Florian d I don’t think that will solve the problem directly - the decoupling of ConfigLoader and logging solves other problem, and it also make sure logging is configured early enough. Previously logging is only initiated after session created so it cannot log things before that.