-
Notifications
You must be signed in to change notification settings - Fork 911
Add details to Asynchronous UpDownCounter API #1704
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
Add details to Asynchronous UpDownCounter API #1704
Conversation
UpDownCounter. To determine the reported rate the Asynchronous UpDownCounter is | ||
changing, the difference between successive measurements is used. | ||
|
||
The callback function SHOULD NOT take indefinite amount of time. If multiple |
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.
similar question on # of exporters per-sdk
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.
Tracked by the discussion here #1703 (comment).
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.
I think the collection cycle suggestion from the thread is great and making this note would be beneficial for the spec. Is there work item to track this ? I don't think we need to block this PR.
enough approvals, cool off period passed, merging. @reyang would you please address the comment about the number of calls to the callback per collection comment? |
Co-authored-by: Sergey Kanzhelev <[email protected]>
Co-authored-by: Trask Stalnaker <[email protected]> Co-authored-by: Joao Grassi <[email protected]>
Follow up #1617.
Changes
Added details to the Asynchronous Gauge instrument. In #1617 these were left as TODO.