grpc / grpc/grpc-dotnet

Logging/Tracing lower than grpc

Open
#2,373 2 comments 0 reactions 0 assignees View on GitHub
question
Dominant language
C#
Stars
4.5k
Forks
836
Avg merge
6d 3h
Merged PRs (30d)
7

Description

I am trying to diagnose an issue I have connecting to my grpc service behind a proxy in Kubernetes. When I create a service and connect to my service directly, all works well, but when I call via the proxy, I get an error message stating that my server returned a 500 error and an error message stating '500 Internal Server Error' caused by: connection error: PROTOCOL_ERROR.

I have tried to use server side interceptors, client side interceptors, asp.net logging middleware, but none seem to be invoked when calling via the proxy. What are my options with respect to tracing/logging/diagnosing this issue?

Thanks in advance,

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.