-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Resources doc - reconsider use of service.name in example #1830
Comments
happy to hear that @geekrypter! If you think you know what needs to be done from the issue description, go ahead and raise a PR with us, we can help you from there. If you have any questions on the issue and what needs to be done upfront, just let us know, either here, in the slack channel (CNCF slack, #otel-comms) or in one of our meetings |
Hi @svrnm, Could you please clarify the following doubts:
|
@geekrypter, thanks!
|
Thanks for the clarification @svrnm! Working on the issue. |
See here: #1795 (comment)
It's more likely that someone setting a service name will do so with the
OTEL_SERVICE_NAME
attribute, or in code, than just as a key-value pair. I would propose that we just put another example there, or remove it.The text was updated successfully, but these errors were encountered: