Ted Young

To clarify, it's possible for an event to only have attributes, and not have a body. But that would likely be an event defined by OpenTelemetry, not an event created...

@alexvanboxel for clarity: attributes in OpenTelemetry are defined as simple data structures, and are intended to be used as indexes or dimensions. The body field is intended for storing complex...

@alexvanboxel do you mean how to describe the body as a semantic convention. Yes we are working on it. You can see an example here: https://github.com/open-telemetry/semantic-conventions/blob/main/model/logs/mobile-events.yaml

Based on this discussion, I've updated #3969 to add logging from shared libraries as a reason to use the Event API.

Hello @kelko! To explain, Events are a replacement for SpanEvents. In OpenTelemetry, all LogRecords include a SpanContext if there is an active trace when they are recorded. It is possible...

@cijothomas no, it is not. To clarify, what I meant was that Events are LogRecords, and are expected to be fed into the Log SDK. As it says in the...

fwiw, while we do have some legacy span attributes that may contain large values, we have since clarified that the intention of attributes is for indexing, not for storing large...

I would be in favor of this! I have concerns around supporting 3rd party loggers wanting to create events. Those loggers would not have a name field, so they would...

But I do think the Name field should be added as an option onto the EmitLogRecord function. In part for the reasons described in the comment above: there may be...

Hi @nirga, I'd like to get this officially approved. Do you mind adding a couple of points to confirm: * What trademarks, if any, that are being donated. Are we...