Skip to content

Generate semconv/v1.40.0 - #7929

Merged
dmathieu merged 5 commits into
open-telemetry:mainfrom
ChrsMark:gen_semconv_1_40
Mar 2, 2026
Merged

dmathieu merged 5 commits into
open-telemetry:mainfrom
ChrsMark:gen_semconv_1_40

Conversation

@ChrsMark

Copy link
Copy Markdown
Member

Signed-off-by: ChrsMark <chrismarkou92@gmail.com>
Signed-off-by: ChrsMark <chrismarkou92@gmail.com>
@codecov

codecov Bot commented Feb 19, 2026 •

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 81.7%. Comparing base (0f1a224) to head (d26c9ef).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files

Impacted file tree graph

@@           Coverage Diff           @@
##            main   #7929     +/-   ##
=======================================
- Coverage   81.7%   81.7%   -0.1%     
=======================================
  Files        304     304             
  Lines      23333   23333             
=======================================
- Hits       19080   19079      -1     
  Misses      3865    3865             
- Partials     388     389      +1     

see 3 files with indirect coverage changes

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@MrAlias MrAlias left a comment •

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This looks good.

I'd like to wait merging this until after the next release. That way we have time to update semconv used here and in contrib.

@MrAlias MrAlias added this to the v1.42.0 milestone Feb 20, 2026
@ChrsMark

Copy link
Copy Markdown
Member Author

Thank's @MrAlias! My intention is to use the new package in the Collector (k8sattributes processor) to validate the promotion of the k8s attributes to Beta.

I'm fine using the package from a merged commit so a release is not necessary.

@ChrsMark

Copy link
Copy Markdown
Member Author

Thank's @MrAlias! My intention is to use the new package in the Collector (k8sattributes processor) to validate the promotion of the k8s attributes to Beta.

I'm fine using the package from a merged commit so a release is not necessary.

@MrAlias @pellared @XSAM @flc1125 WDYT?

@ChrsMark

ChrsMark commented Mar 2, 2026

Copy link
Copy Markdown
Member Author

Hey folks, anything else blocking us here?

@dmathieu
dmathieu merged commit c38a4a5 into open-telemetry:main Mar 2, 2026
39 of 41 checks passed
@dmathieu

dmathieu commented Mar 2, 2026

Copy link
Copy Markdown
Member

I meant to merge this so the package would be available, even if we're not using it. But it seems this makes users unhappy as they upgrade their semantic conventions versions but can't use the latest detectors.

dmathieu added a commit that referenced this pull request Mar 2, 2026
@pellared

pellared commented Mar 2, 2026

Copy link
Copy Markdown
Member

Also #7929 (review)

pellared pushed a commit that referenced this pull request Mar 2, 2026
@ChrsMark

ChrsMark commented Mar 2, 2026

Copy link
Copy Markdown
Member Author

But it seems this makes users unhappy as they upgrade their semantic conventions versions but can't use the latest detectors

@dmathieu @pellared is there a way to decouple the existence of the package from the implementations using this?
Right now using the semconv packages from this repo in the Collector means that we need to wait several weeks.
This is not so convenient. Since those are already released Semantic Conventions it should be implementations' responsibility to make use of them at the right time.

@pellared

pellared commented Mar 2, 2026

Copy link
Copy Markdown
Member

@dmathieu @pellared is there a way to decouple the existence of the package from the implementations using this?

It is decoupled but users were very unsatisfied when these were not updated in the same release.

Right now using the semconv packages from this repo in the Collector means that we need to wait several weeks.

We plan to make 2 subsequent releases quickly. One is already in progress. Next one is mainly about dropping Go 1.24 and adding new semconv.

MrAlias added a commit that referenced this pull request Mar 2, 2026
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.

6 participants