SDKLogLevel field

[pinoOgni]

Hi folks!

I noticed that the SDKLogLevel field in MetricsConfig and in TracesConfig have the same env variable name OTEL_EBPF_SDK_LOG_LEVEL () but the supported values are different.

1. SDKLogLevel in MetricsConfig is used as slog.Level which accepts: debug, info, warn and error
2. SDKLogLevel in TracesConfig is used as zapcore.Level which accepts: debug, info, warn/warning, error, dpanic, panic and fatal

I wanted to change the name of the environment variable, something like OTEL_EBPF_METRICS_SDK_LOG_LEVEL and OTEL_EBPF_TRACES_SDK_LOG_LEVEL, but this is a breaking change, so I'd like to hear your opinion first.

[marctc]

We could add those new env variables but keep the old for now to avoid the breaking change. Is there any reason we have two different loggers? should we try to standardize?

[pinoOgni]

We could add those new env variables but keep the old for now to avoid the breaking change.

Sure

Is there any reason we have two different loggers? should we try to standardize?

Afaik the zapcore logger was added because we need to populate the Logger field inside component.TelemetrySettings struct.

[grcevski]

Would it be possible to translate from the slog log level to the zap log level?

[pinoOgni]

@ajimenez1503 as we discussed this can be a good issue :)

[ajimenez1503]

@ajimenez1503 as we discussed this can be a good issue :)

Thanks. Team could you please asigne to me 😊

[grcevski]

Done thanks again @ajimenez1503 !

[ajimenez1503]

Proposal PR #1250 @grcevski @pinoOgni
Please take a look :)