k

    Katrina P

    2 months ago
    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 😅
    k

    katrina

    2 months ago
    flytectl uses the grpc endpoints under the hood so something like
    flytectl get projects
    should be a simple test
    k

    Katrina P

    2 months ago
    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
    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)
    k

    katrina

    2 months ago
    if you have auth enabled then the logging interceptor should log on every endpoint
    k

    Katrina P

    2 months ago
    what if I do not have auth enabled 😞
    I was able to hit
    get projects
    but dont have logs for it (without auth)
    k

    katrina

    2 months ago
    you could try setting the grpc verbosity env var: https://github.com/grpc/grpc/blob/master/doc/environment_variables.md
    k

    Katrina P

    2 months ago
    I did! The logging shows with pyflyte but not flytectl
    k

    katrina

    2 months ago
    where are you setting that env var? can you set it for the admin service deployment?
    k

    Katrina P

    2 months ago
    Ah, good call, I was setting it on the client, I'll do that