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

Metric SDK - is ExplicitBucketBoundaries advisory stable? #4317

Open
cijothomas opened this issue Dec 3, 2024 · 0 comments
Open

Metric SDK - is ExplicitBucketBoundaries advisory stable? #4317

cijothomas opened this issue Dec 3, 2024 · 0 comments
Labels
spec:metrics Related to the specification/metrics directory triage:accepted:ready Ready to be implemented. Small enough or uncontroversial enough to be implemented without sponsor

Comments

@cijothomas
Copy link
Member

https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/metrics/sdk.md#instrument-advisory-parameters is indicating that Advisory spec for SDK is completely experimental, whereas API spec indicates that the Advisory spec for ExplicitBucketBoundaries is stable and the one for attributes is still experimental.

https://github.com/open-telemetry/opentelemetry-specification/pull/3694/files is the PR where ExplicitBucketBoundaries were marked stable in API, but probably missed SDK part? I can send a PR to make the SDK spec also marked stable for ExplicitBucketBoundaries part if that was the original intent.

@cijothomas cijothomas added the spec:metrics Related to the specification/metrics directory label Dec 3, 2024
@trask trask added the triage:accepted:ready Ready to be implemented. Small enough or uncontroversial enough to be implemented without sponsor label Dec 3, 2024
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 triage:accepted:ready Ready to be implemented. Small enough or uncontroversial enough to be implemented without sponsor
Projects
Status: No status
Development

No branches or pull requests

2 participants