Looking at existing practices on how RPC instrumentations in OTel repos work with OTEL_SEMCONV_STABILITY_OPT_IN:

JS: gRPC instrumentations supports it on server.address | port - https://github.com/open-telemetry/opentelemetry-js/blob/4f0b6285af24b71a9fa022755aaa3b6a63ae5033/experimental/packages/opentelemetry-instrumentation-grpc/README.md?plain=1#L66
python-contrib: no usage among RPC instrumentations - gRPC still uses deprecated net.* attributes - https://github.com/open-telemetry/opentelemetry-python-contrib/blob/2ecc2d24045eedf17d0bf03019dd2fe0703b4024/instrumentation/opentelemetry-instrumentation-grpc/src/opentelemetry/instrumentation/grpc/_server.py#L34
.NET: used to support env var and switched to stable attributes: https://github.com/open-telemetry/opentelemetry-dotnet-contrib/blob/3f072fad9129faf664315253f4f1e1a7394bdc5d/src/OpenTelemetry.Instrumentation.GrpcNetClient/CHANGELOG.md?plain=1#L50
Java - implements new stable conventions - https://github.com/open-telemetry/opentelemetry-java-instrumentation/blob/main/instrumentation/grpc-1.6/library/src/main/java/io/opentelemetry/instrumentation/grpc/v1_6/GrpcNetworkServerAttributesGetter.java
go: no mentions of env var in rpc context, grpc instr sets server.* attrs by default - https://github.com/open-telemetry/opentelemetry-go-contrib/blob/cb62247c5fa2f056d7b2eb47bdd5045038bd6531/instrumentation/google.golang.org/grpc/otelgrpc/stats_handler.go#L322
rust & c++: no mentions
ruby: uses old net.* attributes - https://github.com/open-telemetry/opentelemetry-ruby-contrib/blob/2edff11f55f89cc760695f8bb6422950c492437d/instrumentation/grpc/lib/opentelemetry/instrumentation/grpc/interceptors/client_tracer.rb#L44

tl;dr: it seems only JS actually uses OTEL_SEMCONV_STABILITY_OPT_IN = http on gRPC spans. It should be possible to add support for OTEL_SEMCONV_STABILITY_OPT_IN = rpc in addition to http

Update stability warning for RPC semconv #2718

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions