Vibhu Pandey

+1

Hey @mx-psi, There are no current issues related to this. The background is while using any `auth` extension, we generally want to propagate some data (for example `user_id`) across processors...

Hey @jpkrohling @mx-psi, Any thoughts here?

This is an important feature missing from Signoz. Opentelemetry already has a resource attribute `deployment.environment` which should be a filter option on the services page and all its child pages....

If you look at the `exportCtx` @jpkrohling, it looks like the following: ``` exportCtx := client.NewContext(context.Background(), client.Info{ Metadata: client.NewMetadata(md), }) ``` There is no AuthData preservation happening here at all....

Hey @jpkrohling, Created an issue for this: https://github.com/open-telemetry/opentelemetry-collector/issues/10093

@jpkrohling same test showcasing issue https://github.com/open-telemetry/opentelemetry-collector/issues/10093

Update: If I set a custom context key in my authenticator like : ``` return context.WithValue(ctx, mycustomKey, key), nil ``` and then access it with ``` ctx.Value(mycustomKey) ``` in my...

I guess the root cause is that in grpc an interceptor to enrich the incoming context is called after the extension's auth method which is overwriting the Metadata set by...

@TylerHelmuth Amend the following line located at https://github.com/open-telemetry/opentelemetry-collector/blob/main/config/configgrpc/configgrpc.go#L413: ``` - uInterceptors = append(uInterceptors, enhanceWithClientInformation(gss.IncludeMetadata)) + uInterceptors = append(enhanceWithClientInformation(gss.IncludeMetadata), uInterceptors...) ``` This gives us control over playing with the Metadata in...