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

[Semantic Conventions] Align on the specification 1.13.0 #1625

Merged
merged 3 commits into from
Sep 22, 2022

Conversation

marcalff
Copy link
Member

@marcalff marcalff commented Sep 21, 2022

Fixes #1624

Changes

Upgrade semantic conventions to opentelemetry-specification v1.13.0

BREAKING: rename net.peer.ip to net.sock.peer.addr, net.host.ip to net.sock.host.addr,
net.peer.name to net.sock.peer.name for socket-level instrumentation.

See the opentelemetry-specification v.1.13.0 release notes,
section Semantic Conventions, for full details.

  • CHANGELOG.md updated for non-trivial changes
  • Unit tests have been added
  • Changes in public API reviewed

@marcalff marcalff requested a review from a team September 21, 2022 19:45
@codecov
Copy link

codecov bot commented Sep 21, 2022

Codecov Report

Merging #1625 (ca750f2) into main (909c26d) will not change coverage.
The diff coverage is n/a.

Additional details and impacted files

Impacted file tree graph

@@           Coverage Diff           @@
##             main    #1625   +/-   ##
=======================================
  Coverage   85.06%   85.06%           
=======================================
  Files         159      159           
  Lines        4999     4999           
=======================================
  Hits         4252     4252           
  Misses        747      747           

@ThomsonTan
Copy link
Contributor

@lalitb could you please take a look?

I think we want to include this in the coming patch release. Should this be marked as breaking change, or probably no need as semantic convention itself is not in stable stage?

@lalitb
Copy link
Member

lalitb commented Sep 22, 2022

@lalitb could you please take a look?

I think we want to include this in the coming patch release. Should this be marked as breaking change, or probably no need as semantic convention itself is not in stable stage?

Yes, I think we can mark it as a breaking change, as there may be code changes required for instrumentation libraries. We don't need a major version upgrade as you rightly mentioned it as experimental.

@lalitb lalitb merged commit fe0c62f into open-telemetry:main Sep 22, 2022
yxue pushed a commit to yxue/opentelemetry-cpp that referenced this pull request Dec 5, 2022
yxue pushed a commit to yxue/opentelemetry-cpp that referenced this pull request Dec 5, 2022
@marcalff marcalff deleted the fix_sem_conv_1624 branch July 4, 2023 07:08
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.

[Semantic Conventions] Align on semantic conventions from specification 1.13
3 participants