We use the prefect logging method Either self logger from `T

Question

We use the prefect logging method Either self logger from `Task` or imported from `from prefect utilities logging import get logger` We get some weird double logging with different formats I am not sure if it is a pure Prefect issue or just something we do wrong on our ends But did someone else see something like this an has a solution ``` 2020 08 19 15 21 50 INFO prefect TaskRunner | Task load finished task run for task with final state Success Task load finished task run for task with final state Success 2020 08 19 15 21 51 INFO prefect TaskRunner | Task extract finished task run for task with final state Success Task extract finished task run for task with final state Success 2020 08 19 15 21 51 INFO prefect FlowRunner | Flow run SUCCESS all reference tasks succeeded Flow run SUCCESS all reference tasks succeeded 2020 08 19 15 21 52 INFO prefect orchestrator utils | Flow state transition lt Running Running flow gt gt lt Success All reference tasks succeeded gt Flow state transition lt Running Running flow gt gt lt Success All reference tasks succeeded gt ```

Michael Ludwig · Answer

One of the log formats can be adjusted the other one stay plain when changing this env variable ```export PREFECT LOGGING FORMAT= gt asctime s levelname s name s | message s ```

Michael Ludwig · Answer

When looking at the prefect code and playing with it I can also see that the first StreamHandler is the one giving me problems ```def create logger name str gt logging Logger Creates a logger with a `StreamHandler` that has level and formatting set from `prefect config` Args name str Name to use for logger Returns logging Logger a configured logging object logging setLogRecordFactory log record context injector logger = logging getLogger name handler = logging StreamHandler sys stdout formatter = logging Formatter context config logging format context config logging datefmt formatter converter = time gmtime type ignore handler setFormatter formatter logger addHandler handler logger setLevel context config logging level cloud handler = CloudHandler cloud handler setLevel DEBUG logger addHandler cloud handler return logger```

Michael Ludwig · Answer

Nevermind we figured out that it is because of our own library we use which somehow messes with the root logger smile