We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
As https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/metrics/api.md#asynchronous-counter-creation states:
OpenTelemetry API authors SHOULD define whether this callback function needs to be reentrant safe / thread safe or not.
We should define the reentrant safety of JavaScript Metrics API callbacks.
The text was updated successfully, but these errors were encountered:
The spec has updated to define that:
Callback functions MUST be documented as follows for the end user: Callback functions SHOULD be reentrant safe. The SDK expects to evaluate callbacks for each MetricReader independently. Callback functions SHOULD NOT take an indefinite amount of time. Callback functions SHOULD NOT make duplicate observations (more than one Measurement with the same attributes) across all registered callbacks.
Callback functions MUST be documented as follows for the end user:
We should follow the latest definition.
Sorry, something went wrong.
Successfully merging a pull request may close this issue.
As https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/metrics/api.md#asynchronous-counter-creation states:
We should define the reentrant safety of JavaScript Metrics API callbacks.
The text was updated successfully, but these errors were encountered: