[chore] Remove SHOULD for compiler name in process.runtime.name
.
#1221
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
It seems a bit misleading to generally recommend that compiled languages include the native compiler name as the
process.runtime.name
attribute. With golang as a notable exception (due to the runtime being a compilation byproduct), I don't think the compiler names make much sense here otherwise.If the specific compiler details are important to have in telemetry, then they should get their own first-class attributes, rather than piggy-backing on
process.runtime.name
.I couldn't find any other support for this in the semconv nor rust nor cpp implementations. I think the behavior described below for Go is perfectly reasonable and I left it untouched.
Changes
Removes the SHOULD recommendation for including the compiler name in the
process.runtime.name
.Merge requirement checklist
[chore]