Skip to content
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

Semantic attributes for language runtime #830

Closed
anuraaga opened this issue Aug 19, 2020 · 1 comment · Fixed by #882
Closed

Semantic attributes for language runtime #830

anuraaga opened this issue Aug 19, 2020 · 1 comment · Fixed by #882
Labels
area:semantic-conventions Related to semantic conventions release:after-ga Not required before GA release, and not going to work on before GA spec:resource Related to the specification/resource directory

Comments

@anuraaga
Copy link
Contributor

anuraaga commented Aug 19, 2020

Looked around and couldn't find these, does it make sense to have semantic attributes for a language runtime? For example

process.runtime.name - a name of a runtime, for example Oracle JDK, .Net Core, PyPy
process.runtime.version version of the runtime in runtime.name

For compiled languages I guess we wouldn't fill them, though putting information about the compiler (if available) could be an option.

@anuraaga anuraaga added the spec:resource Related to the specification/resource directory label Aug 19, 2020
@arminru arminru added the area:semantic-conventions Related to semantic conventions label Aug 19, 2020
@arminru
Copy link
Member

arminru commented Aug 19, 2020

I think it would make sense to add this 👍
For the runtime name I suggest adding a list of well-known values like we have for the database vendor (db.system) in the semantic conventions for DB calls.

@bogdandrutu bogdandrutu added the release:after-ga Not required before GA release, and not going to work on before GA label Aug 19, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area:semantic-conventions Related to semantic conventions release:after-ga Not required before GA release, and not going to work on before GA spec:resource Related to the specification/resource directory
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants