Skip to content

[Tracer|Meter|Logger]Configurator and [Tracer|Meter|Logger]Config to be optional #4644

@pellared

Description

@pellared

Specify that [Tracer|Meter|Logger]Configurator and [Tracer|Meter|Logger]Config MAY be implemented by the SDK (they are not required).

The Go SIG does not want to implement these features.

We want to implement the declarative configuration using via processors.

We are fine with the proposal given we want to implement this configuration using (internally) LogRecordProcessors. We do not want to add LoggerConfigurator into the Go Logs SDK, because we find it unnecessary as everything should be achievable using LogRecordProcessor. The experience for the end-user should remain the same.

Note that we already have:

Enabled is an operation that a LogRecordProcessor MAY implement

for languages that do not want to support Logger.Enabled via processors.

The same should be done for [Tracer|Meter|Logger]Configurator and [Tracer|Meter|Logger]Config.

CC @open-telemetry/go-maintainers

Originally posted by @pellared in #4612 (comment)

Metadata

Metadata

Assignees

Labels

area:sdkRelated to the SDKclarificationclarify ambiguity in specificationmaintainer-requestEscalated by SIG maintainersspec:logsRelated to the specification/logs directoryspec:metricsRelated to the specification/metrics directoryspec:traceRelated to the specification/trace directorytriage:deciding:community-feedbackOpen to community discussion. If the community can provide sufficient reasoning, it may be accepted

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions