Logging updates

[wild-endeavor]

TL;DR

Cleaning up logging a bit. Existing behavior should remain unchanged.

Continue to use the FLYTE_SDK_LOGGING_LEVEL var to control logging across flytekit. This level will be used to set the log handler level, so it affects all loggers.

By default it's set to warning and higher.

Type

• Bug Fix
• Feature
• Plugin

Are all requirements met?

• Code completed
• Smoke tested
• Unit tests added
• Code documentation added
• Any pending items have an associated Issue

Complete description

Also added some new environment variables that introduce additional granularity, but this api should be considered to be beta, and is subject to change.

The hello world example now produces these logs:

{"asctime": "2021-12-13 19:40:20,113", "name": "flytekit.entrypoint", "levelname": "INFO", "message": "Welcome to Flyte! Version: 0.0.0+develop"}
{"asctime": "2021-12-13 19:40:20,113", "name": "flytekit.entrypoint", "levelname": "DEBUG", "message": "Running task execution with resolver flytekit.core.python_auto_container.default_task_resolver..."}
{"asctime": "2021-12-13 19:40:20,114", "name": "flytekit.entrypoint", "levelname": "INFO", "message": "Using user directory /tmp/flyte/20211213_194019/sandbox/local_flytekit/69004e6eb271ffd5ca43bc6128899eda"}
{"asctime": "2021-12-13 19:40:20,121", "name": "flytekit.entrypoint", "levelname": "DEBUG", "message": "Starting _dispatch_execute for core.flyte_basics.hello_world.say_hello"}
{"asctime": "2021-12-13 19:40:20,349", "name": "flytekit.entrypoint", "levelname": "INFO", "message": "Engine folder written successfully to the output prefix s3://my-s3-bucket/metadata/propeller/flytesnacks-development-rx2abgp0eg/n0/data/0"}
{"asctime": "2021-12-13 19:40:20,349", "name": "flytekit.entrypoint", "levelname": "DEBUG", "message": "Finished _dispatch_execute"}

This is with the following set:

ENV FLYTE_SDK_LOGGING_LEVEL 10
ENV FLYTE_SDK_LOGGING_LEVEL_ROOT 30
ENV FLYTE_SDK_LOGGING_LEVEL_ENTRYPOINT 10

but again, users should not rely on the latter two remaining as is forever. Configuration of granularity, assuming it continues to be exposed (which is not certain) may change.