Conversation
|
The question I have is whether or not its appropriate to stabilize part of the event spec while other key parts remain in development. In particular, I'm thinking of the semantic convention guidance on usage of attributes and body. Is this part of the spec close to being stable? I've been involved in various discussions which suggest that there is still active debate, but I may be incorrectly reading the room. |
This does not change the need of having the EventName.
I am more in favor of iterative and incremental development. Especially in places where we already have consensus. This gives opportunity to get more feedback and experience with part of that we are uncertain. The decision how to use attributes vs body would not remove the need of a dedicated event name field. |
mattmccleary
left a comment
There was a problem hiding this comment.
In the long-run, I think this will benefit the industry as a first step at standardizing and unifying the language we use re logs, events, etc.
|
No objection from my side. |
### Context - Add context propagation through Environment Variables specification. ([#4454](#4454)) - On Propagators API, stabilize `GetAll` on the `TextMap` Extract. ([#4472](#4472)) ### Traces - Define sampling threshold field in OpenTelemetry TraceState; define the behavior of TraceIdRatioBased sampler in terms of W3C Trace Context Level 2 randomness. ([#4166](#4166)) ### Metrics - Clarify SDK behavior for Instrument Advisory Parameter. ([#4389](#4389)) ### Logs - Add `Enabled` opt-in operation to the `LogRecordProcessor`. ([#4439](#4439)) - Stabilize `Logger.Enabled`. ([#4463](#4463)) - Stabilize `EventName`. ([#4475](#4475)) ### Baggage - Add context (baggage) propagation through Environment Variables specification. ([#4454](#4454)) ### Resource - Add Datamodel for Entities. ([#4442](#4442)) ### SDK Configuration - Convert declarative config env var substitution syntax to ABNF. ([#4448](#4448)) - List declarative config supported SDK extension plugin interfaces. ([#4452](#4452)) --------- Co-authored-by: Armin Ruech <7052238+arminru@users.noreply.github.com>
Fixes #4459
From the issue comments:
See also: open-telemetry/opentelemetry-proto#643