semconv stable code

[SylvainJuge]

Semconv 1.33.0 brings stable definitions for code.* namespace, which includes the following changes:

• code.namespace is removed
• code.function is renamed to code.function.name and needs to include fully-qualified name of the class in addition to the function
• code.lineno has been renamed code.line.number
• code.column has been renamed code.column.number
• code.filepath has been renamed code.file.path

This PR might have to be updated if merged after the update to semconv 1.33.0 is merged first. EDIT: updated after 1.34.0 semconv update

EDIT: the existing code.* semantic conventions are still produced, the stable ones are opt-in by setting the otel.semconv-stability.opt-in config option to include code (only stable) or code/dup (both stable + old).

[otelbot-java-instrumentation]

🔧 The result from spotlessApply was committed to the PR branch.

[otelbot-java-instrumentation]

🔧 The result from spotlessApply was committed to the PR branch.

[SylvainJuge]

I have updated this PR to only emit the deprecated semantic convention attributes by default.
Most instrumentation remain tested with unstable attributes, but some (like log appenders) are tested with both.

Using otel.semconv-stability.opt-in configuration allows to opt-in for the new stable semantic conventions with code or code/dup like we have for the database attributes, so it means we could merge this PR without altering the current behavior.

Then, we could then later remove the support for the unstable code attributes when preparing for the 3.0 release.

Is there already an issue that contains a list of breaking changes that we are planning to include in this major release to track progress on their respective implementations ? If no, please let me know and I can create one so we don't forget about this (and also the database semconv).

[trask]

Is there already an issue that contains a list of breaking changes that we are planning to include in this major release to track progress on their respective implementations ?

https://github.com/open-telemetry/opentelemetry-java-instrumentation/milestone/41

[SylvainJuge]

Is there already an issue that contains a list of breaking changes that we are planning to include in this major release to track progress on their respective implementations ?

https://github.com/open-telemetry/opentelemetry-java-instrumentation/milestone/41

Thanks, I've opened #14059.

@trask your review status is still "requested change", do you think there are still things to change before we could merge this ?

stale

[trask]

thanks!

[trask]

🎉