You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When generating semantic conventions with otel/semconvgen:0.24.0 I notice that messaging.client.id is duplicated: one "deprecated" and one "normal"
Steps to Reproduce (if any)
Expected Result
Only one entry for messaging.client.id
Actual Result
Semantic convention version
1.26.0
Additional context
I think what's going on is that whichever code generates a const name from a semconv attribute, is ending up with the same answer for messaging.client.id and messaging.client_id (note the _ vs .). We use {{ attribute.fqn | to_const_name }}
The text was updated successfully, but these errors were encountered:
Area(s)
area:messaging
What happened?
Description
When generating semantic conventions with otel/semconvgen:0.24.0 I notice that
messaging.client.id
is duplicated: one "deprecated" and one "normal"Steps to Reproduce (if any)
Expected Result
Only one entry for
messaging.client.id
Actual Result
Semantic convention version
1.26.0
Additional context
I think what's going on is that whichever code generates a const name from a semconv attribute, is ending up with the same answer for
messaging.client.id
andmessaging.client_id
(note the_
vs.
). We use{{ attribute.fqn | to_const_name }}
The text was updated successfully, but these errors were encountered: