gRPC trace propagation/continuation

[aldy505]

Problem Statement

I will write in details later, but TLDR: We have one for HTTP and it's in the convention (docs here: https://docs.sentry.io/platforms/javascript/guides/node/tracing/distributed-tracing/), but we don't have that for gPRC.

Solution Brainstorm

Maybe add the custom header name on the ServerOptions (

sentry-go/grpc/server.go

Lines 24 to 33 in 9b7a562

	type ServerOptions struct {
	// Repanic determines whether the application should re-panic after recovery.
	Repanic bool
	// WaitForDelivery determines if the interceptor should block until events are sent to Sentry.
	WaitForDelivery bool
	// Timeout sets the maximum duration for Sentry event delivery.
	Timeout time.Duration
	}

)? Therefore:

type ServerOptions struct {
	// Repanic determines whether the application should re-panic after recovery.
	Repanic bool

	// WaitForDelivery determines if the interceptor should block until events are sent to Sentry.
	WaitForDelivery bool

	// Timeout sets the maximum duration for Sentry event delivery.
	Timeout time.Duration

	SentryTraceHeaderKey string
	BaggageHeaderKey string
}

[linear-code]

GO-148

[giortzisg]

Is this for W3C? We already propagate sentry trace.

[aldy505]

How do we propagate it for grpc? Any docs?

[linear-code]

from giannisgkiortzis:

You just use ContinueFromHeaders as in any other case. sentry-trace and baggage should already be already there.