https://flyte.org
Join Slack
Anyone have a good way of testing the grpc end points (maybe with grpcurl) to debug networking issue...
# flyte-deployment
l
Anyone have a good way of testing the grpc end points (maybe with grpcurl) to debug networking issues? I upped the admin logging level, and hoping to see more logs to see if we're hitting admin correctly but can't tell if there's just no logs or if we're not hitting it 😅
a
flytectl uses the grpc endpoints under the hood so something like 
flytectl get projects
should be a simple test
l
Something like ... 
flytectl get projects --logger.level=6 --admin.insecure  --admin.endpoint dns:///host:81
or 
flytectl get projects --logger.level=6 --admin.insecure  --admin.endpoint {ip}:81
✅ 1
And if I have logging level at 20 in my admin config I should be able to see admin logging requests right? I just want to make sure since the logs don't seem to outputting anything (which would suggest we're not hitting it)
a
if you have auth enabled then the logging interceptor should log on every endpoint
l
what if I do not have auth enabled 😞
I was able to hit 
get projects
but dont have logs for it (without auth)
a
you could try setting the grpc verbosity env var: https://github.com/grpc/grpc/blob/master/doc/environment_variables.md
l
I did! The logging shows with pyflyte but not flytectl
a
where are you setting that env var? can you set it for the admin service deployment?
l
Ah, good call, I was setting it on the client, I'll do that
201 Views
Open in Slack
PreviousNext
Powered by

Flyte

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

Powered by