Open jsuereth opened 4 months ago
We are no longer changing how constants are named. We will either be dropping deprecated names or keeping both with different names in some way.
Based on the conclusion in https://github.com/open-telemetry/semantic-conventions/issues/1118#issuecomment-2173803006, we need to be able to resolve codegen conflicts at semconv definition time.
E.g.:
messaging.client_id
should be marked as dropped in code, see for the details https://github.com/open-telemetry/semantic-conventions/issues/1031#issuecomment-2173887975. The same option could be used for other low-usage attributesSome ideas
dropping old
attributes:
- id: foo.bar_baz
deprecated: "Use `foo.bar.baz` instead"
code_friendly_name: none # new, optional property, defaults to snake_case(id)
preserving old and giving new attribute new code const name
attributes:
- id: foo.bar_baz
deprecated: "Use `foo.bar.baz` instead"
- id: foo.bar.baz
code_friendly_name: foo_bar_baz2
Defining code-friendly name for not supported characters
- id: pprof::foo.bar
code_friendly_name: pprof_foo_bar
See https://github.com/open-telemetry/semantic-conventions/issues/1118 for context