Bryan Whiting
01/24/2023, 10:50 PMexport PREFECT__LOGGING__LEVEL=DEBUG
def main():
logger = get_run_logger()
logger.warning("warning")
logger.debug("debug")
<http://logger.info|logger.info>("info")
logger.critical("critical")
yet the debug isn’t printing:
14:49:20.921 | WARNING | Flow run 'wonderful-hamster' - warning
14:49:20.921 | INFO | Flow run 'wonderful-hamster' - info
14:49:20.922 | CRITICAL | Flow run 'wonderful-hamster' - critical
Nate
01/24/2023, 11:12 PMPREFECT_LOGGING_LEVEL
? the setting name has single underscores
❯ prefect config set PREFECT__LOGGING__LEVEL="DEBUG"
Unknown setting name 'PREFECT__LOGGING__LEVEL'.
❯ prefect config set PREFECT_LOGGING_LEVEL="DEBUG"
Set 'PREFECT_LOGGING_LEVEL' to 'DEBUG'.
Timo Vink
01/24/2023, 11:18 PMprefect
is imported. Setting it after prefect is imported but before get_run_logger
is called isn't early enough.Bryan Whiting
01/24/2023, 11:19 PMPREFECT__LOGGING__LEVEL=DEBUG
Nate
01/24/2023, 11:20 PMBryan Whiting
01/24/2023, 11:20 PMNate
01/24/2023, 11:21 PMPREFECT_LOGGING_LEVEL
at the profile level whenever you like (relative to package import) using the prefect config set KEY=VAL
not sure off the top about the timing when using a standard shell env varTimo Vink
01/24/2023, 11:25 PMos.environ
. Profile indeed seems like the better way to set this!