-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
sdk/metric: Remove Reader.ForceFlush and ManualReader.ForceFlush #4375
sdk/metric: Remove Reader.ForceFlush and ManualReader.ForceFlush #4375
Conversation
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## main #4375 +/- ##
=====================================
Coverage 78.8% 78.8%
=====================================
Files 253 253
Lines 20645 20644 -1
=====================================
+ Hits 16280 16283 +3
+ Misses 4016 4012 -4
Partials 349 349
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM pending the acceptance at the specification level.
There is no consensus on specification PR, but I looks like all objections are NOT related to changes proposed in this PR. E.g. see: open-telemetry/opentelemetry-specification#3609 (review). Still, I prefer to wait and consider it as blocked. |
Now blocked on open-telemetry/opentelemetry-specification#3563 PS. During the last specification SIG meeting nobody was against this approach. |
open-telemetry/opentelemetry-specification#3563 is merged 🎉 |
Co-authored-by: Tyler Yahn <MrAlias@users.noreply.github.com>
Why
The
Reader.ForceFlush
andManualReader.ForceFlush
are not needed and we can remove it to make the user-facing API cleaner. E.g. we do not need the Prometheus exporter to haveForceFlush
(via type embedding ofmetric.Reader
).ForceFlush
is only required when periodic reader is used. This change is now possible after #4244.The OTel Specification does NOT require to require to have
Reader.ForceFlush
. For instance the OTel .NET SDK readers do not implementForceFlush
at all.Related PRs and issues in specification:
What
Remove
Reader.ForceFlush
andManualReader.ForceFlush
. Use type assertions so thatForceFlush
is properly handled by theMetricProvider
.