mirror of
https://github.com/fnproject/fn.git
synced 2022-10-28 21:29:17 +03:00
e637661ea2
* Adding a way to inject a request ID It is very useful to associate a request ID to each incoming request, this change allows to provide a function to do that via Server Option. The change comes with a default function which will generate a new request ID. The request ID is put in the request context along with a common logger which always logs the request-id We add gRPC interceptors to the server so it can get the request ID out of the gRPC metadata and put it in the common logger stored in the context so as all the log lines using the common logger from the context will have the request ID logged
23 lines
728 B
Go
23 lines
728 B
Go
// Copyright 2017 Michal Witkowski. All Rights Reserved.
|
|
// See LICENSE for licensing terms.
|
|
|
|
/*
|
|
`grpc_opentracing` adds OpenTracing
|
|
|
|
OpenTracing Interceptors
|
|
|
|
These are both client-side and server-side interceptors for OpenTracing. They are a provider-agnostic, with backends
|
|
such as Zipkin, or Google Stackdriver Trace.
|
|
|
|
For a service that sends out requests and receives requests, you *need* to use both, otherwise downstream requests will
|
|
not have the appropriate requests propagated.
|
|
|
|
All server-side spans are tagged with grpc_ctxtags information.
|
|
|
|
For more information see:
|
|
http://opentracing.io/documentation/
|
|
https://github.com/opentracing/specification/blob/master/semantic_conventions.md
|
|
|
|
*/
|
|
package grpc_opentracing
|