-
Notifications
You must be signed in to change notification settings - Fork 896
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Stabilizing service.name #1497
Comments
For reference this came up because we don't have a stable way for configuring the service name in Java |
👍 for making it stable. But we should consider it together with |
+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. |
@thisthat Is this something we can add to the yaml tool? |
@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! |
Fixed by #3202 |
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.The text was updated successfully, but these errors were encountered: