semconv stable code#13860
Conversation
|
🔧 The result from spotlessApply was committed to the PR branch. |
…nstrumentation into semconv-stable-code
…nstrumentation into semconv-stable-code
|
🔧 The result from spotlessApply was committed to the PR branch. |
|
I have updated this PR to only emit the deprecated semantic convention attributes by default. Using Then, we could then later remove the support for the unstable 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). |
|
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 ? |
…nstrumentation into semconv-stable-code
…nstrumentation into semconv-stable-code
|
🎉 |
Semconv 1.33.0 brings stable definitions for
code.*namespace, which includes the following changes:code.namespaceis removedcode.functionis renamed tocode.function.nameand needs to include fully-qualified name of the class in addition to the functioncode.linenohas been renamedcode.line.numbercode.columnhas been renamedcode.column.numbercode.filepathhas been renamedcode.file.pathThis 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 updateEDIT: the existing
code.*semantic conventions are still produced, the stable ones are opt-in by setting theotel.semconv-stability.opt-inconfig option to includecode(only stable) orcode/dup(both stable + old).