Flyte enables production-grade orchestration for machine learning workflows and data processing created to accelerate local workflows to production.

Flyte

Hi team.. while running the workflow in the local sandbox, is there a way to view the k8s logs? The k8s dashboard asks for a token or a config

there is some work in progress to fetch the logs in a separate service

I still don't see anything logged using python's logging library

Looks like I may need to use _`flytekit.current_context().logging` ?_

do you see any logs in the console for the workflow execution?

which console? I went to node-&gt;executions-&gt;K8s logs

I see nothing other than the stack backtrace

if you're running demo it should be available here: <http://localhost:30080/console>

when you use pyflyte run, it will output a link to the execution as well!

like here: <https://docs.flyte.org/en/latest/getting_started/index.html#executing-workflows-on-a-flyte-cluster>

oh that console.. yes I'm looking at the console

when I click on view logs for failed task it opens the pane on the right. I click k8s logs but I don't see any of the actual logs

other than the stack trace from the failure

<@U03HQE6THNV> when you click k8s logs and it takes you to the kubernetes console can you change the namespace to `flytesnacks-development` (or whatever corresponds to the &lt;project&gt;-&lt;domain&gt; you ran your workflow under) and see if there are pods there that correspond to your execution id?

ohh Rupsha you are running Flyte demo on a remote machine right

then you will have to port forward or change the endpoint

<http://localhost:30082/#/log/myproject-development/fcc656e1c3bf54d2ea9d-n4-0/pod?namespace=myproject-development&amp;container=fcc656e1c3bf54d2ea9d-n4-0>

And the only thing I see is the stack trace

looks like ONLY error logs show up.. not info

oh I wonder if you need to set the log level: <https://github.com/flyteorg/flytekit/blob/b400a1ba6a79ee1fd784665ab768fb08917e729f/flytekit/loggers.py#L12>

I believe in the container definition cc <@U0265RTUJ5B>

correct.
<@U03HQE6THNV>, can you set that env var to `20`?

so in the dockerfile I set
`ENV LOGGING_ENV_VAR 20` ?