Support for Semantic Convention schema migrations #8495
Comments
|
https://github.com/open-telemetry/opentelemetry-go/tree/main/schema was created with the goal of enabling this type of translation, both within the SDK and in the collector. |
|
Hey @alolita , could I ask you to move this to the contrib repo? |
Done! |
|
Love your work @jpkrohling <3 |
**Description:** As part of the [accepted specification](https://github.com/open-telemetry/opentelemetry-specification/blob/e16e1a781bdf62a8fcfa1a12963844749de23e7a/specification/schemas/overview.md#collector-assisted-schema-transformation), there needs to be a processor within the collector that is able to allow for transformations of semantic convention versions . This is my initial draft, I wrote this before https://github.com/open-telemetry/opentelemetry-collector-contrib/pull/8344/files shared their solution to it. **Link to tracking Issue:** #8495 Original raised in the collector but should be shifted to the contrib a I can tell. **Testing:** It currently does nothing and there is the initial testing set up within the components. **Documentation:** Added a minimal README, will expand upon it once more work has been added to the collector.
**Description:** As part of the [accepted specification](https://github.com/open-telemetry/opentelemetry-specification/blob/e16e1a781bdf62a8fcfa1a12963844749de23e7a/specification/schemas/overview.md#collector-assisted-schema-transformation), there needs to be a processor within the collector that is able to allow for transformations of semantic convention versions . This is my initial draft, I wrote this before https://github.com/open-telemetry/opentelemetry-collector-contrib/pull/8344/files shared their solution to it. **Link to tracking Issue:** open-telemetry#8495 Original raised in the collector but should be shifted to the contrib a I can tell. **Testing:** It currently does nothing and there is the initial testing set up within the components. **Documentation:** Added a minimal README, will expand upon it once more work has been added to the collector.
|
This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping |
|
Sorry, I am back to working on this. I just need to rebase and catch up on what i have missed. |
|
This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping |
MovieStoreGuy
added
never stale
|
I created https://github.com/MrAlias/otel-schema-utils to help with opentelemetry-go users who needed to translate resources created at different schema versions. It is not a complete translation suite, but I thought I would post it here in case it would be helpful to anyone trying to resolve this issue. |
Is your feature request related to a problem? Please describe.
As means of supporting varies versions of the semantic convention, it would be nice to emit only one version of the semantic convention and migrate anyone using an older version to target X.
Describe the solution you'd like
The collector has the ability to be configured to emit a given version of the semantic convention and translate older attributes into the new attributes or resource names (metric name, span name) to the updated convention.
Describe alternatives you've considered
Ideally this should be resolve by pushing out auto instrumentation and letting the apps upgrade as there is a new version, but isn't always easier to get right. It would also help getting large monolith projects onto the new semantic conventions but schema migrations.
Additional context
This was discussed in the last APAC instrumentation meeting and is a nice to have to help allow fast iterations on the semantic convention.
cc @tedsuo
The text was updated successfully, but these errors were encountered: