Stabilizing service.name

[anuraaga]

Currently all attributes are experimental, for example we see the Experimental label.

https://www.github.com/open-telemetry/opentelemetry-specification/tree/main/specification%2Fresource%2Fsemantic_conventions%2FREADME.md

But service.name is required to use Zipkin or Jaeger - those exporters are also effectively experimental because of this dependency. Is it possible to mark this attribute stable? I guess we should add support to the yaml generator for stable attributes if so.

[anuraaga]

For reference this came up because we don't have a stable way for configuring the service name in Java

open-telemetry/opentelemetry-java#2973

[Oberon00]

👍 for making it stable. But we should consider it together with service.namespace, as they are closely related. The instance ID stuff should not be made stable yet though, see #1034.

[rakyll]

+1 to considering to stabilize the name with namespace. We are thinking about representing service identifiers as a first-class thing in the backends. We should think about the service identity as namespace + name.

[anuraaga]

@thisthat Is this something we can add to the yaml tool?

[thisthat]

@anuraaga sorry for the late reply! Sure, this can be added to the tool! Currently, we support only deprecated attributes. It would be easy to add other markers!

[jsuereth]

Fixed by #3202