Jack Berg
Jack Berg
Note this PR was discussed / requested in this discussion: https://github.com/open-telemetry/opentelemetry-java/discussions/7473 If folks can review, I think we should move forward with this PR. Its still valuable and low risk.
@jkwatson I think there's a possible race condition. - OtlpHttpLogRecordExporter (and other exports) capture internal metrics with a lazily initialized meter from `GlobalOpenTelemetry`. See [here](https://github.com/open-telemetry/opentelemetry-java/blob/main/exporters/common/src/main/java/io/opentelemetry/exporter/internal/http/HttpExporterBuilder.java#L63). - BatchLogRecordProcessor's worker thread [starts...
> I just want to clarify that for comparing these cases is not fair as for Logger.Enabled we already have experimental support in OTel Logs SDK with examples for Context...
We discussed in the points about process from [this comment](https://github.com/open-telemetry/opentelemetry-specification/pull/4262#pullrequestreview-2373690154) in the 10/23/24 TC meeting. The question is: **Should we add spec process language requiring that API proposals have corresponding...
> What if we do not have any prototype but we know that for Go it will be very hard to add this parameter in future if it will become...
Left a [comment](https://github.com/open-telemetry/opentelemetry-specification/issues/4207#issuecomment-2450783947) on the issue about Context parameter of Logger#enabled, which is intertwined with the proposal of this PR.
> maybe just suppress the requirement to add a comment to each suppression? Yeah let's do that to get this merged. I do like the concept tho so let's open...
Oof I want this but.. 1. Even with breaking changes allowed in ExtendedOpenTelemetry, they still cause churn and we don't want to offer a capability and later have to withdraw...
FYI @open-telemetry/configuration-approvers, this is the last really important tooling change I see. #397 is a nice to have, but with this merged, we can do a `ctrl + f` in...
FYI, for anyone following this issue, the issue #4384 linked above has been closed. Please see the issue for details.