otlptracegrpc v2

[pellared]

The scope of this issue is to create a new otlptracegrpc v2 module which would have API similar to otlpmetricgrpc.

Unfortunately, it is not possible (without making a breaking change) to remove the dependency on google.golang.org/grpc in otlptracehttp because of https://pkg.go.dev/go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracehttp#NewClient as https://pkg.go.dev/go.opentelemetry.io/otel/exporters/otlp/otlptrace#Client exposes the proto package which depends on google.golang.org/grpc.

The fix would require creating v2 modules. For oteltracehttp and oteltracegrpc. After these are created we still need to support the v1 modules for at least a year. I think for ease of review we should create the new v2 modules of otlptracehttp and otlptracegrpc "from scratch" (similar to otlploghttp).

More: #5221

Originally posted by @pellared in #2579 (comment)

[MrAlias]

We should only accept a grpc conn for the new package options instead of creating our own.

[pellared]

We should only accept a grpc conn for the new package options instead of creating our own.

I think we should do the same for otlploggrpc, right?

Related issue: #5056
CC @XSAM

[dashpole]

We should only accept a grpc conn for the new package options instead of creating our own.

Can we also keep DialOptions? It much more convenient, and allows passing many of the other options we support. I think we should keep the v1 of the otlploggrpc exporter consistent with the other signals, unless we plan to release a v2 of the others before we release the v1 of otlploggrpc.

[XSAM]

We should only accept a grpc conn for the new package options instead of creating our own.

Can we also keep DialOptions? It much more convenient, and allows passing many of the other options we support. I think we should keep the v1 of the otlploggrpc exporter consistent with the other signals, unless we plan to release a v2 of the others before we release the v1 of otlploggrpc.

If we keep WithDialOption, we might also need to provide WithEndpoint, as the grpc.NewClient needs an endpoint unless we want to force our users to use env to provide the endpoint.

[XSAM]

So, maybe we should just keep the WithGRPCConn.

[dashpole]

I would support keeping WithEndpoint as well in that case.

[MrAlias]

We should only accept a grpc conn for the new package options instead of creating our own.

Can we also keep DialOptions? It much more convenient, and allows passing many of the other options we support. I think we should keep the v1 of the otlploggrpc exporter consistent with the other signals, unless we plan to release a v2 of the others before we release the v1 of otlploggrpc.

@dashpole can you provide some examples here? I'm not sure I follow how passing options via our WithDialOptions is easier than directly to the grpc.NewClient function.

I'm not opposed to keeping things the way they are in other modules, but I would want to better understand how our API is an improvement before copying it.

[MrAlias]

A use case the NewClient only option wouldn't support:

• You want to pass client auth to be used
• You also want to use environment variables or the defaults for endpoint, path, ...

The client only solution would mean you need to reproduce all the default/envar stuff on your own.