SemanticConventions attribute name constants differ from spec

[tshowers-bt]

Bug Report

OpenTelemetry.SemanticConventions 1.0.0-rc9.9

Symptom

I notice that some of the constants in the package don't match the values in the spec; for example public const string AttributeMessagingMessageId = "messaging.message_id"; but the spec refers to messaging.message.id.

The PR that introduced this says the values were autogenerated so maybe it's just out of date? I had a quick look at the build-tools and it links to the java package which has a constant that does match the spec.

[Kielek]

New tag is was released as 1.17.0: https://github.com/open-telemetry/opentelemetry-specification/blob/3d594588815fa4564fe35984e8b1a714e54d48f2/CHANGELOG.md?plain=1#L91

Current semantic convention was generated from 1.13.0 https://github.com/open-telemetry/opentelemetry-dotnet/blob/main/src/OpenTelemetry.SemanticConventions/scripts/semantic-conventions/generate.ps1#L6

Is there any chance that you create PR with regenerated code?

[tshowers-bt]

I'll certainly have a go at it. Probably later today.

[ttd2089]

I opened a PR but simply updating the versions didn't work. I found this issue and had to add a volume mount to the docker run command to fix the problem; but now I'm not sure whether the generated output is actually correct. As mentioned in the PR there are some properties in the generated code that I didn't see in the corresponding diff in the semconv changelog:

• code.column
• messaging.source.kind
• messaging.source.template