You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am using most of go-grpc-middleware and I have a question regarding logs. I wish to include the payload in the standard output or have a way to correlate both of them.
One simple way could be to pass a GUID in the context and flag both logs with it. Then we could aggregate both results in Grafana. It' not optimal but would work, though. 🤔
By the way, thanks for the amazing work!
The text was updated successfully, but these errors were encountered:
jhayotte
changed the title
grpc_logging payloads embedded in the standard output
grpc_logging payloads embedded in the classic log output
Mar 27, 2018
So the reason why the payload is separate is to facilitate streaming requests: one log entry per emitted payload. This way you can flash statements as they come.
As for tagging, that's already supported. Both interceptors should be automatically adding whatever you're getting from grpc_ctxtags to every log statement made.
We are using it together with grpc_opentracing to get a request trace/span number automatically tagged.
Hi,
I am using most of go-grpc-middleware and I have a question regarding logs. I wish to include the payload in the standard output or have a way to correlate both of them.
In order to get, ideally, this king of output:
Below, an extract of my interceptor.
One simple way could be to pass a GUID in the context and flag both logs with it. Then we could aggregate both results in Grafana. It' not optimal but would work, though. 🤔
By the way, thanks for the amazing work!
The text was updated successfully, but these errors were encountered: