-
Notifications
You must be signed in to change notification settings - Fork 893
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
Provide clear guidance on what semconv actually enforces #3225
Conversation
…by semconv that can be included in stability.
Co-authored-by: Trask Stalnaker <[email protected]>
Co-authored-by: Trask Stalnaker <[email protected]>
Co-authored-by: Johannes Tax <[email protected]>
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.
Thanks for tackling this @jsuereth
I think it is important to define precisely what we guarantee.
Co-authored-by: Tigran Najaryan <[email protected]>
Co-authored-by: Carlos Alberto Cortez <[email protected]>
…`faas.max_memory` (open-telemetry#3209)
* Add connect_rpc to rpc.yaml * Add connect rpc into rpc-metrics and rpc markdown * Add Connect RPC change to CHANGELOG.md * Update CHANGELOG.md --------- Co-authored-by: Armin Ruech <[email protected]>
Co-authored-by: Yuri Shkuro <[email protected]>
Co-authored-by: Trask Stalnaker <[email protected]>
Co-authored-by: Trask Stalnaker <[email protected]>
Co-authored-by: Trask Stalnaker <[email protected]>
Co-authored-by: Trask Stalnaker <[email protected]>
Co-authored-by: jack-berg <[email protected]>
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 have no objection to additions done in the PR, but I still have concern wrt schema transformation and how/if it can really guarantee stability and work along with this PR.
I created #3296 and suggest that we keep schema transformations experimental with possibility to stabilize it in the future independently of current efforts to stabilize HTTP semconv.
Co-authored-by: Liudmila Molkova <[email protected]>
…try#3225) Fixes open-telemetry#2864 Fixes open-telemetry#2883 ## Changes - Explicitly define what is "enforced" by stability guarantees from Semantic conventions. - We enforce attribute key names + types, across resource, span, metric and log - We enforce span names - We enforce metric names, units - Expand allowed changes to semconv to include metric attributes that do not increase timeseries count for a given metric. ## Context Sig discussion thread/doc [here](https://docs.google.com/document/d/1Nvcf1wio7nDUVcrXxVUN_f8MNmcs0OzVAZLvlth1lYY/edit?usp=sharing). --------- Co-authored-by: Trask Stalnaker <[email protected]> Co-authored-by: Johannes Tax <[email protected]> Co-authored-by: Tigran Najaryan <[email protected]> Co-authored-by: Patrice Chalin <[email protected]> Co-authored-by: Sergey Kanzhelev <[email protected]> Co-authored-by: Carlos Alberto Cortez <[email protected]> Co-authored-by: Tyler Benson <[email protected]> Co-authored-by: Joshua Carpeggiani <[email protected]> Co-authored-by: Armin Ruech <[email protected]> Co-authored-by: Yuri Shkuro <[email protected]> Co-authored-by: Asaf Mesika <[email protected]> Co-authored-by: Evan Mattson <[email protected]> Co-authored-by: jack-berg <[email protected]> Co-authored-by: Antoine Toulme <[email protected]> Co-authored-by: Christian Neumüller <[email protected]> Co-authored-by: Liudmila Molkova <[email protected]> Co-authored-by: Reiley Yang <[email protected]> Co-authored-by: Joshua MacDonald <[email protected]>
Fixes #2864
Fixes #2883
Changes
Context
Sig discussion thread/doc here.