Skip to content

[process] Promote Process to RC#3758

Merged
kamphaus merged 3 commits into
open-telemetry:mainfrom
osullivandonal:promote-process-to-RC
Jun 24, 2026
Merged

[process] Promote Process to RC#3758
kamphaus merged 3 commits into
open-telemetry:mainfrom
osullivandonal:promote-process-to-RC

Conversation

@osullivandonal

@osullivandonal osullivandonal commented May 29, 2026

Copy link
Copy Markdown
Contributor

Fixes #3041

Changes

This work promotes process metrics and entity to RC.

Process Executable was not promoted due to it potentially changing, see comment here.

Important

Pull requests acceptance are subject to the triage process as described in Issue and PR Triage Management.
PRs that do not follow the guidance above, may be automatically rejected and closed.

Merge requirement checklist

  • CONTRIBUTING.md guidelines followed.
  • Change log entry added, according to the guidelines in When to add a changelog entry.
    • If your PR does not need a change log, start the PR title with [chore]
  • Links to the prototypes or existing instrumentations (when adding or changing conventions)

This work promotes process metrics and entity to RC.
@osullivandonal
osullivandonal requested review from a team as code owners May 29, 2026 10:08
@github-actions github-actions Bot added enhancement New feature or request area:process labels May 29, 2026
@lmolkova lmolkova moved this from Untriaged to Awaiting codeowners approval in Semantic Conventions Triage Jun 1, 2026
@osullivandonal

Copy link
Copy Markdown
Contributor Author

@open-telemetry/specs-semconv-maintainers this is approved by the SIG, please take a look.

@github-project-automation github-project-automation Bot moved this from Awaiting codeowners approval to Needs More Approval in Semantic Conventions Triage Jun 8, 2026
@jsuereth jsuereth moved this from Needs More Approval to Ready to be Merged in Semantic Conventions Triage Jun 8, 2026
@jsuereth
jsuereth added this pull request to the merge queue Jun 8, 2026
@github-merge-queue
github-merge-queue Bot removed this pull request from the merge queue due to failed status checks Jun 8, 2026
@github-project-automation github-project-automation Bot moved this from Ready to be Merged to Needs More Approval in Semantic Conventions Triage Jun 8, 2026
@kamphaus kamphaus moved this from Needs More Approval to Ready to be Merged in Semantic Conventions Triage Jun 8, 2026
@kamphaus
kamphaus added this pull request to the merge queue Jun 8, 2026
@github-merge-queue
github-merge-queue Bot removed this pull request from the merge queue due to failed status checks Jun 8, 2026
@kamphaus

kamphaus commented Jun 8, 2026

Copy link
Copy Markdown
Contributor

@joaopgrassi

Copy link
Copy Markdown
Member

The merge queue had failing policies-check: open-telemetry/semantic-conventions/actions/runs/27147348462/job/80128662933

@kamphaus looks fine now.. did you change anything? 🤔

@lmolkova
lmolkova added this pull request to the merge queue Jun 10, 2026
@github-merge-queue
github-merge-queue Bot removed this pull request from the merge queue due to failed status checks Jun 10, 2026
@kamphaus

Copy link
Copy Markdown
Contributor

The merge queue runs checks after merging into main.
It looks like the policy changes from #3752 are blocking.

Try merging the latest main into osullivandonal:promote-process-to-RC

@osullivandonal

osullivandonal commented Jun 15, 2026

Copy link
Copy Markdown
Contributor Author

This work fails on the CI policies-check, see here. There are 3 attributes used by process metrics that have a stability of development:

Diagnostic report:

Violation: semconv_attribute
  - Message   : id=Group 'metric.process.disk.io' has stability 'release_candidate' which is higher than the stability 'development' of attribute 'disk.io.direction'; lower-stability attributes are only allowed at 'opt_in' requirement level, category=group_stability_violation, group=metric.process.disk.io, attr=disk.io.direction
  - Level     : violation
  - Context   :
    - attr : disk.io.direction
    - category : group_stability_violation
    - group : metric.process.disk.io
    - id : Group 'metric.process.disk.io' has stability 'release_candidate' which is higher than the stability 'development' of attribute 'disk.io.direction'; lower-stability attributes are only allowed at 'opt_in' requirement level
  - Provenance: /home/weaver/source

Violation: semconv_attribute
  - Message   : id=Group 'metric.process.network.io' has stability 'release_candidate' which is higher than the stability 'development' of attribute 'network.io.direction'; lower-stability attributes are only allowed at 'opt_in' requirement level, category=group_stability_violation, group=metric.process.network.io, attr=network.io.direction
  - Level     : violation
  - Context   :
    - attr : network.io.direction
    - category : group_stability_violation
    - group : metric.process.network.io
    - id : Group 'metric.process.network.io' has stability 'release_candidate' which is higher than the stability 'development' of attribute 'network.io.direction'; lower-stability attributes are only allowed at 'opt_in' requirement level
  - Provenance: /home/weaver/source

Violation: semconv_attribute
  - Message   : id=Group 'metric.process.paging.faults' has stability 'release_candidate' which is higher than the stability 'development' of attribute 'system.paging.fault.type'; lower-stability attributes are only allowed at 'opt_in' requirement level, category=group_stability_violation, group=metric.process.paging.faults, attr=system.paging.fault.type
  - Level     : violation
  - Context   :
    - attr : system.paging.fault.type
    - category : group_stability_violation
    - group : metric.process.paging.faults
    - id : Group 'metric.process.paging.faults' has stability 'release_candidate' which is higher than the stability 'development' of attribute 'system.paging.fault.type'; lower-stability attributes are only allowed at 'opt_in' requirement level
  - Provenance: /home/weaver/source

I am going to open a separate PR to mark these attributes as release candidate.

PR opened to Promote the above attributes to RC: #3796

@trask

trask commented Jun 15, 2026

Copy link
Copy Markdown
Member

Looks like this is failing a recently added policy check that stability level on the group must be the same or higher than all non opt-in attributes.

@lmolkova lmolkova moved this from Ready to be Merged to Blocked in Semantic Conventions Triage Jun 22, 2026
@osullivandonal

Copy link
Copy Markdown
Contributor Author

Looks like this is failing a recently added policy check that stability level on the group must be the same or higher than all non opt-in attributes.

I have merged from main, all checks now pass, we merged the PR #3796 which promoted the required attributes to RC which was blocking here.

@open-telemetry/specs-semconv-maintainers this work is now unblocked and good to be merged.

@kamphaus kamphaus moved this from Blocked to Ready to be Merged in Semantic Conventions Triage Jun 24, 2026
@kamphaus
kamphaus added this pull request to the merge queue Jun 24, 2026
Merged via the queue into open-telemetry:main with commit a03df15 Jun 24, 2026
18 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area:process enhancement New feature or request

Projects

Archived in project

Development

Successfully merging this pull request may close these issues.

Stabilize the process namespace

10 participants