Aaron Abbott

Also, thanks for trying things out.

Thanks for opening this. This has recently been added to the spec as the "Advisory API": https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/metrics/api.md#instrument-advisory-parameter-explicitbucketboundaries So we just need someone to implement this :)

@LarsMichelsen thank you for the summary in https://github.com/open-telemetry/opentelemetry-python/issues/4044#issuecomment-2223671513, I agree with your conclusions. In particular: > - Users which configured the timeout in seconds, would once interpreted as milliseconds, provide...

> Also, even if they notice this, changing the deployments to introduce this temporary environment variable seems to be work that people would simply not do. > > I think...

Follow up to the SIG discussion: @xrmx's concern is fixing this in a timely manner. @open-telemetry/python-maintainers is there any objection or downside to doing a major version bump? The only...

The fix in #3429 might be the culprit. IIRC the previous behavior (see https://github.com/open-telemetry/opentelemetry-python/issues/3407) was that histograms would not be sent from the SDK to the exporter if there had...

@colincadams what is your export interval? You may be able to achieve similar cost savings by exporting less often

To recap the context from OP: > I'll start with a rough conceptual proposal: > > 1. The exporter uses `self._timeout` (based on `OTEL_EXPORTER_OTLP_TIMEOUT`, defaults to 10 sec) as maximum...

> We already do this today with the `instrumentation` and `exporter` packages, which extend the OTel Python API package. I think the reasoning behind `opentelemetry.instrumentation` and `opentelemetry.exporter` was simply namespacing...

@codeboten sorry for the delay. I'm gonna unassign myself for now in case any one else has time to pick it up cc @lzchen