Skip to content
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

Clarify the API on behavior of asynchronous callback reentrancy, timeout, duplicate observations #2350

Open
jmacd opened this issue Feb 15, 2022 · 0 comments
Assignees
Labels
spec:metrics Related to the specification/metrics directory

Comments

@jmacd
Copy link
Contributor

jmacd commented Feb 15, 2022

What are you trying to achieve?

The current specification is vague on what happens if an asynchronous instrument callback times out, on what happens if the same SDK or different SDK needs to call invoke the callbacks before another collection finishes. Also, requirements are written that impact the user, so the API specification should be phrased as a requirement to document what is expected of the user, not specify the user's behavior.

What did you expect to see?

More rigor on what SDKs should do, what kind of reentrancy guarantees should be expected for callbacks.

Additional context.

Questions arose in #2317:

#2317 (comment)
#2317 (comment)
#2317 (comment)

cc/ @dyladan @legendecas @anuraaga

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
spec:metrics Related to the specification/metrics directory
Projects
None yet
Development

No branches or pull requests

2 participants