Why does the logs bridge API not support TraceID & SpanID?

[sekthor]

The go.opentelemetry.io/otel/sdk/log implementation of the log Record has fields for traceID and spanID.

opentelemetry-go/sdk/log/record.go

Lines 81 to 82 in 4958732

	traceID trace.TraceID
	spanID trace.SpanID

However the go.opentelemetry.io/otel/log implementation (which I understand to be the Log Bridge API), does not have these fields.
Consequentially, I could not find log bridges implementing support for it.

Intuitively, I would expect a logger that supports some variation of WithContext(context.Context)-function to be able to read traceID and spanID from this context and set these values in the log record.

Testing a logbridge (logrus) with stdoutlog and could see, that these fields are printed, yet I could find no way to set these fileds.

Is this not supported?

An example record shows that these fileds present, but set to nil-values (shortened for readability).

{
    "Timestamp": "2024-12-20T13:06:06.932664699+01:00",
    "ObservedTimestamp": "2024-12-20T13:06:06.932669144+01:00",
    "Severity": 9,
    "SeverityText": "",
    "Attributes": [],
    "TraceID": "00000000000000000000000000000000",
    "SpanID": "0000000000000000",
    "TraceFlags": "00",
    "Resource": [],
    "Scope": {},
    "DroppedAttributes": 0
}

Or am I just using the API wrong?

[sekthor]

Turns out I was just being stuipid and everything is working as expected.