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 SDK behavior for Instrument Advisory Parameter #4389

Merged
merged 21 commits into from
Mar 18, 2025

Conversation

cijothomas
Copy link
Member

Also Fixes #4317

Changes

Mostly editorial, to specify SDK behavior for Advisory Parameters, explicitly calling out that SDK MUST give precedence to View config over InstrumentAdvisory. I believe this is already the intention, but was less specified. Though some wordings exist in the View spec about attribute-keys, no mention about Histogram buckets..

@cijothomas cijothomas requested review from a team as code owners January 28, 2025 18:48
Copy link

github-actions bot commented Mar 7, 2025

This PR was marked stale due to lack of activity. It will be closed in 7 days.

@github-actions github-actions bot added the Stale label Mar 7, 2025
@carlosalberto
Copy link
Contributor

Maybe take a last look @jack-berg ?

@cijothomas
Copy link
Member Author

@carlosalberto could you merge?

@carlosalberto carlosalberto merged commit d83c63d into open-telemetry:main Mar 18, 2025
6 checks passed
@cijothomas cijothomas deleted the cijothomas/fix4317 branch March 20, 2025 21:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Metric SDK - is ExplicitBucketBoundaries advisory stable?
8 participants