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

Provide clear guidance on what semconv actually enforces #3225

Merged
merged 46 commits into from
Apr 3, 2023

Conversation

jsuereth
Copy link
Contributor

Fixes #2864
Fixes #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.

…by semconv that can be included in stability.
@jsuereth jsuereth requested review from a team February 17, 2023 14:57
specification/versioning-and-stability.md Outdated Show resolved Hide resolved
specification/versioning-and-stability.md Outdated Show resolved Hide resolved
jsuereth and others added 2 commits February 17, 2023 12:28
Co-authored-by: Trask Stalnaker <trask.stalnaker@gmail.com>
Co-authored-by: Trask Stalnaker <trask.stalnaker@gmail.com>
Copy link
Member

@tigrannajaryan tigrannajaryan left a 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.

specification/versioning-and-stability.md Outdated Show resolved Hide resolved
specification/versioning-and-stability.md Outdated Show resolved Hide resolved
specification/versioning-and-stability.md Outdated Show resolved Hide resolved
specification/versioning-and-stability.md Outdated Show resolved Hide resolved
specification/versioning-and-stability.md Outdated Show resolved Hide resolved
specification/versioning-and-stability.md Show resolved Hide resolved
jsuereth and others added 10 commits February 21, 2023 15:01
Co-authored-by: Tigran Najaryan <4194920+tigrannajaryan@users.noreply.github.com>
Co-authored-by: Carlos Alberto Cortez <calberto.cortez@gmail.com>
* 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 <armin.ruech@dynatrace.com>
Co-authored-by: Yuri Shkuro <yurishkuro@users.noreply.github.com>
jsuereth and others added 4 commits March 2, 2023 11:23
Co-authored-by: Trask Stalnaker <trask.stalnaker@gmail.com>
Co-authored-by: Trask Stalnaker <trask.stalnaker@gmail.com>
Co-authored-by: Trask Stalnaker <trask.stalnaker@gmail.com>
Co-authored-by: Trask Stalnaker <trask.stalnaker@gmail.com>
Co-authored-by: jack-berg <34418638+jack-berg@users.noreply.github.com>
Copy link
Contributor

@lmolkova lmolkova left a 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.

specification/versioning-and-stability.md Outdated Show resolved Hide resolved
specification/versioning-and-stability.md Outdated Show resolved Hide resolved
Co-authored-by: Liudmila Molkova <limolkova@microsoft.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet