Track differences between the OpenTelemetry spec and the .NET implementation of the logs bridge API

[juliuskoval]

The purpose of this issue is to keep track of all the differences between the .NET implementation of the logs bridge API and the OpenTelemetry specification as suggested by @Kielek here.

Get a Logger

The API MUST accept these parameters:

• schema_url - optional, not implemented
• attributes - optional, not implemented

Logger

• The Logger SHOULD provide functions to report if it is enabled (not implemented)

Emit a LogRecord

The API MUST accept these parameters:

• Timestamp - implemented as DateTime, should be optional
• Observed timestamp - optional, currently in core review Add ObservedTimestamp to LogRecordData #6979
• Body - optional. Implemented as string, but should be AnyValue according to the spec.
• Attributes - optional. Implemented as KeyValuePair<string, object?>, but should be collection of AnyValue
• The Context associated with the LogRecord. The .NET implementation doesn't seem to have Context as defined in the spec. The closest thing seems to be Activity.Current. The API accepts ActivityTraceId and ActivitySpanId which can be used in place of Activity for this purpose.

The API MAY accept the following parameter:

• Exception - optional, currently in code review Add Exception to LogRecordData #6980. The current implementation has the LogRecordAttributeList.RecordException method instead.

Enabled

Not implemented

Ergonomic API

Still in development, not implemented

Tip

_{React with 👍 to help prioritize this issue. Please use comments to provide useful context, avoiding +1 or me too, to help us triage it. Learn more here.}