Hey I m noticing that none of the logs we produce in our var

Question

Hey I m noticing that none of the logs we produce in our various tasks are actually surfaced when viewing pod logs I only see the flytekit warnings about pickle types is there something in particular we need to set to make logging work

Ketan (kumare3) · Answer

Log level

Rahul Mehta · Answer

Thanks < Ketan kumare3 > Is this set during serialization or as part of the decorators or elsewhere

Ketan (kumare3) · Answer

Cc < Yee>

Yee · Answer

how are you doing logging rahul we re going to do some work cleaning up how logging works in flytekit next month

Yee · Answer

the environment variable to set is `FLYTE SDK LOGGING LEVEL=10` for debug

Rahul Mehta · Answer

We re using the normal `logging` environment and info level logs appear to be suppressed

Yee · Answer

like just import logging

Yee · Answer

so that won t change then with our updates you ll need to update that manually

Yee · Answer

Yee · Answer

these are the current flytekit loggers they were designed to be as out of the way as possible from the normal python logging constructs

Rahul Mehta · Answer

that == the env var

Yee · Answer

no that == the issue of logging not coming up

Yee · Answer

but also yes setting that won t affect anything

Rahul Mehta · Answer

Hmm alright are there any other things I should try taking a look at

Yee · Answer

you ll need to call basicConfig I think

Yee · Answer

one sec

Yee · Answer

digging up something

Yee · Answer

this is the thread I m going through <https discuss flyte org t 1019 of course Thank you for digging into this and using force is>

Yee · Answer

yeah so flytekit doesn t get completely out of the way because any call to logging without a root handler will trigger a call to basicConfig so you ll need to call basicConfig with a force

Yee · Answer

note that this is all python logging sematics very little to do with flyte

Yee · Answer

however we also attach the user logger created in that loggers py file to the flytekit user context so you can do ```flytekit current context <http logging info|logging info> ``` for that to show though you ll need to set that environment variable above

Yee · Answer

does this make sense

Rahul Mehta · Answer

I think so will read through that discussion first