Stabilize Logger.Enabled

[pellared]

Stabilize Logger.Enabled API

Blockers:

• Define Enabled parameters for Logger #4203
• Specify how Logs SDK implements Enabled #4207
• Do not require extensible Logger.Enabled parameters list  #4221
• Add Enabled to LogRecordProcessor #4363
• (optional, no use cases so far) Add EventName parameter to Logger.Enabled #4220

[pellared]

Question to @open-telemetry/technical-committee: Do we want to stabilize the Logger.Enabled API sooner than we stabilize the spec defining how SDK implements it? Or do we want to stabilize Enabled for API and SDK at the same time?

[cijothomas]

Question to @open-telemetry/technical-committee: Do we want to stabilize the Logger.Enabled API sooner than we stabilize the spec defining how SDK implements it? Or do we want to stabilize Enabled for API and SDK at the same time?

Same for Metrics too: https://github.com/open-telemetry/opentelemetry-specification/pull/4219/files#r1767789558

[pellared]

The lack of stabilization of Logger.Enabled API blocks stabilization of OTel Go Logs.
Logger.Enabled API is required for bridging most popular Go logging libraries (including slog from the Go standard library).

From OTel Go perspective, the SDK support can be experimental. See: https://pkg.go.dev/go.opentelemetry.io/otel/sdk/log/internal/x.

This is currently the only known blocker for stabilizing the OTel Go Logs.