Hey all With GCP the logs before user code is executed are a

Question

Hey all With GCP the logs before user code is executed are all coming up as severity=ERROR I d love to try to fix this at some point and was wondering if anyone has thoughts Ideally this could be configurable too I was talking to < Yee> about this earlier and he suggested posting here for visibility I also made a GitHub

Yee · Answer

greg any interest in seeing what it would take to make this a pluggable system

Yee · Answer

some members of the community will appreciate the flexibility and some others would probably rather keep log keys from changing

Greg Gydush · Answer

more env variables

Greg Gydush · Answer

that s how I would probably hack it together

Greg Gydush · Answer

otherwise it would have to go in Flyte s configuration elsewhere

Greg Gydush · Answer

or via plugin registration

Greg Gydush · Answer

but are loggers an okay use for plugins

Yee · Answer

plugin registration you didn t like right

Yee · Answer

because lots of flytekit internal logging would still print

Greg Gydush · Answer

not if it runs before the plugins

Greg Gydush · Answer

like the first plugin is logger

Yee · Answer

we can sort it i m sure

Greg Gydush · Answer

first logs are from plugins it looks like

Yee · Answer

`discovered plugins = entry points group= flytekit plugins ` we can sort this to have loggers first

Yee · Answer

but that feels a bit hacky

Yee · Answer

open to suggestions

Yee · Answer

maybe an option to disable the logger

Yee · Answer

and an option to add another one

Greg Gydush · Answer

a plugin for logger with a sensible default sounds nice and then we can just have a specific GCP logger implementation that handles the severity setting stuff with jsonlogger

Greg Gydush · Answer

I figured out a workaround for myself that I like

Greg Gydush · Answer

will add it to the GitHub issue

Greg Gydush · Answer