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've been using go-kit for some times now (high five for the amazing work !) and have been developing micro-services on Kubernetes and istio where istio tracing is leveraged. If interested in supporting istio tracing through simple header propagation (istio doc), I have working code that I would be happy to push through a pull request.
Basically the code implements the function func ServerBefore(before ...RequestFunc) ServerOption for HTTP and gRPC
Specifically tailored to Istio I think it does not provide a whole lot of value. I do see where one could have a generic "baggage" like header propagation middleware for clients and servers with the ability to specifically whitelist or blacklist which headers to allow or deny for propagation.
By the way if you want to have Go kit interop in distributed tracing you can already do so. Go kit supports Zipkin, OpenTracing and OpenCensus instrumentation thus you can use these to already propagate traces (and even augment traces with local in process spans).
Hi, thanks for your reply. I understand, makes sense. Today, the trend is to offload middlewares to the service mesh as much as possible : middlewares like
JWT verification
request tracing
circuit breakers
fault injections
etc (see istio features)
however tracing or accessing custom claims in JWT (for example) still require to propagate requests' headers to downstream services. This is two areas where header propagation has been implemented in our backends. So your suggestion of a generic "baggage" middleware for header propagation makes sense to me.
Hi guys,
I've been using go-kit for some times now (high five for the amazing work !) and have been developing micro-services on Kubernetes and istio where istio tracing is leveraged. If interested in supporting istio tracing through simple header propagation (istio doc), I have working code that I would be happy to push through a pull request.
Basically the code implements the function
func ServerBefore(before ...RequestFunc) ServerOption
for HTTP and gRPCdefined here
so that header values can be saved in the
context
, and then inject to every downstream requests.Is it something you see being pushed to your code base ? Let me know.
Cheers
The text was updated successfully, but these errors were encountered: