[internal/core] migrate semconv from v1.12.0#46533
[internal/core] migrate semconv from v1.12.0#46533ChrsMark merged 23 commits intoopen-telemetry:mainfrom
Conversation
Signed-off-by: Paulo Dias <paulodias.gm@gmail.com>
Signed-off-by: Paulo Dias <paulodias.gm@gmail.com>
Signed-off-by: Paulo Dias <paulodias.gm@gmail.com>
Signed-off-by: Paulo Dias <paulodias.gm@gmail.com>
ChrsMark
left a comment
There was a problem hiding this comment.
Given that it's a breaking change on the schema, did we considered doing it following the https://github.com/open-telemetry/opentelemetry-collector/blob/main/docs/rfcs/semconv-feature-gates.md?
Not really, I was not aware of this RFC at all. I'll look into it. |
Signed-off-by: Paulo Dias <paulodias.gm@gmail.com>
|
@ChrsMark Thank you, I added the changes behind feature gates in the following commit, PTAL. @MovieStoreGuy @frzifus PTAL again, as I changed the behaviour to be behind a feature gate as the RFC asks to avoid being a breaking change. If everything is ok, I'll create issues to move this feature gates to |
Signed-off-by: Paulo Dias <paulodias.gm@gmail.com>
Signed-off-by: Paulo Dias <paulodias.gm@gmail.com>
Signed-off-by: Paulo Dias <paulodias.gm@gmail.com>
…-contrib into feat/45076 Signed-off-by: Paulo Dias <paulodias.gm@gmail.com>
…lector-contrib into feat/45076 Signed-off-by: Paulo Dias <paulodias.gm@gmail.com>
Signed-off-by: Paulo Dias <paulodias.gm@gmail.com>
…-contrib into feat/45076 Signed-off-by: Paulo Dias <paulodias.gm@gmail.com>
Signed-off-by: Paulo Dias <paulodias.gm@gmail.com>
…lector-contrib into feat/45076 Signed-off-by: Paulo Dias <paulodias.gm@gmail.com>
Signed-off-by: Paulo Dias <paulodias.gm@gmail.com>
Signed-off-by: Paulo Dias <paulodias.gm@gmail.com>
|
@ChrsMark please take another look |
<!--Ex. Fixing a bug - Describe the bug and how this fixes the issue. Ex. Adding a feature - Explain what this achieves.--> #### Description Add feature gates to migrate deprecated semconv v1.12.0 attributes to their v1.38.0 equivalents in pkg/translator/zipkin and internal/coreinternal/goldendataset, following the [semconv feature gates RFC](https://github.com/open-telemetry/opentelemetry-collector/blob/main/docs/rfcs/semconv-feature-gates.md). Both gates default to disabled, preserving the existing behavior. Users can opt in to the migration at their own pace. Zipkin translator (`pkg.translator.zipkin.*`): - `net.host.ip` -> `network.local.address` - `net.peer.ip` -> `network.peer.address` goldendataset (`internal.coreinternal.goldendataset.*`): - `net.host.ip` -> `network.local.address` - `net.peer.ip` -> `network.peer.address` - `http.host` -> `server.address` - `http.server_name` -> `server.address` Migration path: Enable `<component>.EmitV1NetworkConventions` to start emitting both old and new keys (dual-emit transition) Once user pipelines and backends are updated, also enable `<component>.DontEmitV0NetworkConventions` to stop emitting the deprecated v1.12.0 keys. Initially, this was split into 2 PRs, but the open-telemetry#46534 is also a dependency for this one, so I checked out the code for this PR and closed that one. <!-- Issue number (e.g. open-telemetry#1234) or full URL to issue, if applicable. --> #### Link to tracking issue Fixes open-telemetry#45076 open-telemetry#45041 <!--Describe what testing was performed and which tests were added.--> #### Testing Tested locally without any error. --------- Signed-off-by: Paulo Dias <paulodias.gm@gmail.com>
<!--Ex. Fixing a bug - Describe the bug and how this fixes the issue. Ex. Adding a feature - Explain what this achieves.--> #### Description Add feature gates to migrate deprecated semconv v1.12.0 attributes to their v1.38.0 equivalents in pkg/translator/zipkin and internal/coreinternal/goldendataset, following the [semconv feature gates RFC](https://github.com/open-telemetry/opentelemetry-collector/blob/main/docs/rfcs/semconv-feature-gates.md). Both gates default to disabled, preserving the existing behavior. Users can opt in to the migration at their own pace. Zipkin translator (`pkg.translator.zipkin.*`): - `net.host.ip` -> `network.local.address` - `net.peer.ip` -> `network.peer.address` goldendataset (`internal.coreinternal.goldendataset.*`): - `net.host.ip` -> `network.local.address` - `net.peer.ip` -> `network.peer.address` - `http.host` -> `server.address` - `http.server_name` -> `server.address` Migration path: Enable `<component>.EmitV1NetworkConventions` to start emitting both old and new keys (dual-emit transition) Once user pipelines and backends are updated, also enable `<component>.DontEmitV0NetworkConventions` to stop emitting the deprecated v1.12.0 keys. Initially, this was split into 2 PRs, but the open-telemetry#46534 is also a dependency for this one, so I checked out the code for this PR and closed that one. <!-- Issue number (e.g. open-telemetry#1234) or full URL to issue, if applicable. --> #### Link to tracking issue Fixes open-telemetry#45076 open-telemetry#45041 <!--Describe what testing was performed and which tests were added.--> #### Testing Tested locally without any error. --------- Signed-off-by: Paulo Dias <paulodias.gm@gmail.com>
Description
Add feature gates to migrate deprecated semconv v1.12.0 attributes to their v1.38.0 equivalents in pkg/translator/zipkin and internal/coreinternal/goldendataset, following the semconv feature gates RFC.
Both gates default to disabled, preserving the existing behavior. Users can opt in to the migration at their own pace.
Zipkin translator (
pkg.translator.zipkin.*):net.host.ip->network.local.addressnet.peer.ip->network.peer.addressgoldendataset (
internal.coreinternal.goldendataset.*):net.host.ip->network.local.addressnet.peer.ip->network.peer.addresshttp.host->server.addresshttp.server_name->server.addressMigration path:
Enable
<component>.EmitV1NetworkConventionsto start emitting both old and new keys (dual-emit transition)Once user pipelines and backends are updated, also enable
<component>.DontEmitV0NetworkConventionsto stop emitting the deprecated v1.12.0 keys.Initially, this was split into 2 PRs, but the #46534 is also a dependency for this one, so I checked out the code for this PR and closed that one.
Link to tracking issue
Fixes #45076 #45041
Testing
Tested locally without any error.