mark code.* attributes as release candidate

[SylvainJuge]

Relates to #1377

Changes

This PR marks the non-deprecated code.* attributes as release candidate.

Merge requirement checklist

• CONTRIBUTING.md guidelines followed.
• Change log entry added, according to the guidelines in When to add a changelog entry.
  • If your PR does not need a change log, start the PR title with [chore]
• schema-next.yaml updated with changes to existing conventions.

[trask]

let's mark as release candidate first, we don't have a great way to do that yet, but you can follow pattern used in #1101

[lmolkova]

I support this change.

A few things we should also update:

• https://github.com/open-telemetry/semantic-conventions/blob/main/docs/general/attributes.md#source-code-attributes
  • the section should be marked as release candidate
  • we should update the text there which is out-of-date (talks about spans).
• I hope we can give some guidance there on what/when would populate code attributes.
  • Do we know which components would do it?
  • Are there specific spans/metrics/logs definitions that reference these attributes?

[SylvainJuge]

I have opened #1624 for the naming changes suggestions, it contains a list of all the repositories that would be impacted.

[SylvainJuge]

Now that #1624 and #1677 are now merged, we should be able to move this forward and mark the attributes as release-candidate, so I've refreshed the PR and it should now be ready to review.

[jsuereth]

Approved but would like to see @task's proposed changes merged

[pellared]

Shouldn't we first have a release with code.namespace marked as deprecated?

Otherwise, we are just removing code.namespace and this changelog entry does not make sense: https://github.com/SylvainJuge/semantic-conventions/blob/0acdb7241e968c434d0fe279a6bfd375642d13ce/.chloggen/1646.yaml

[lmolkova]

@pellared it's already deprecated

semantic-conventions/model/code/registry-deprecated.yaml

Line 39 in 1711bc3

deprecated: Value should be included in `code.function.name` which is expected to be a fully-qualified name.

this PR only removed the reference to it from the attribute group and didn't change anything about the attribute definition. That's a common practice we follow in semconv and it's not breaking code-gen.

[pellared]

Per

That's a common practice we follow in semconv and it's not breaking code-gen.

[SylvainJuge]

Thanks for merging this !

What are the usual next steps after release candidate promotion ?

My understanding is that it's probably like this, feel free to comment if there are missing pieces:

• wait for a semconv release (1.31.0) with code.* in RC
• open another PR to promote to stable
• wait for another semconv release (1.32.0) with code.* stable
• start updating usages of code.* semconv to the new stable attributes: maybe this work needs to start when RC attributes are available.

[pellared]

start updating usages of code.* semconv to the new stable attributes

Already done in OTel Go:

• otelslog, otelzap: align with code attributes semantic conventions opentelemetry-go-contrib#6870