Hey all, Is there a way to bind a new field to the...
# flyte-support
b
Hey all, Is there a way to bind a new field to the flyte logger, so it will be shown when flyte catches and logs an exception?
t
not formally - but could you elaborate? you’re referring to user logs? or the flytekit internal logs?
b
I have an id that can help me identify which dataset had an exception when I use my logger (loguru) this id is binded to every log (as seen in logz.io) but when flyte encounters a user exception, the log only contains kubernetes related fields, not my custom data id.
t
but if you add logs using your own logger, they work right? you see the ids
b
yes, the only issue is that it doesnt work for exceptions unless I wrap the whole task with a try except block.
t
there’s no formal api for this… because the logger was supposed to mainly be for flytekit itself.
could you write up an issue for this - and include how you’d like this to be configured?
if there is to be a new api, would like it to be as useful/clean as possible
b
Sure, thanks!