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
The text was updated successfully, but these errors were encountered:
pellared
added
spec:logs
Related to the specification/logs directory
sig-issue
A specific SIG should look into this before discussing at the spec
labels
Nov 4, 2024
I created this issue as I think it was brought up a few times.
My personal opinion, is that for sake of simplicity we should only have Event Name as string for the identifier. The reason is that it is the model of OpenTelemetry Events and not any possible event system/library/software. The OTel Semantic Conventions are using names.
What are you trying to achieve?
It may be good to allow having EventId of an integer type (instead of EventName which is always as string) for performance reasons.
Additional context.
In .NET the EventId is a integer with optional name.
https://learn.microsoft.com/en-us/dotnet/api/microsoft.extensions.logging.eventid.-ctor?view=net-8.0
Also see OTel C++:
Related to:
The text was updated successfully, but these errors were encountered: