Update process attribute requirement levels#3461
Merged
lmolkova merged 10 commits intoopen-telemetry:mainfrom Mar 9, 2026
Merged
Update process attribute requirement levels#3461lmolkova merged 10 commits intoopen-telemetry:mainfrom
lmolkova merged 10 commits intoopen-telemetry:mainfrom
Conversation
- Set `process.pid` and `process.creation.time` as required (Identity). - Set `process.executable.name` to Required (Description). - Set other process descriptive attributes to Optional (`opt_in`). - Update `docs/resources/process.md` to reflect the new requirement levels. This changes ensures consistent process identification and description across all platforms.
process descriptive attribute `process.executable.name` has been updated to optional as this can change with execve calls
mx-psi
approved these changes
Feb 23, 2026
ChrsMark
reviewed
Feb 24, 2026
exception to process.owner and process.command
Contributor
Author
|
It was decided in the System semconv WG SIG that this PR is to just update the process attribute requirement levels, other work such as moving |
rogercoll
approved these changes
Mar 2, 2026
ChrsMark
approved these changes
Mar 2, 2026
kamphaus
approved these changes
Mar 2, 2026
dmitryax
approved these changes
Mar 5, 2026
Member
|
@open-telemetry/specs-semconv-maintainers this one is approved by the SIG, please take a look. |
lmolkova
approved these changes
Mar 9, 2026
This was referenced Mar 11, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Related to #864
Changes
process.pidandprocess.creation.timeas required (process Identity).Setprocess.executable.nameto required (Description).opt_in).docs/resource/process.mdto reflect the new requirement levels.This change ensures consistent process identification and description across all platforms.
- The reason that the process identifier entities have been marked asrequiredis they are consistently available across all platforms. These provide a solid way to identify a process.-process.executable.namehas been made required as this is also available across all platforms.- For example:- Linux this is available from either
/proc/(pid)/comm or /proc/(pid)/status.- Windows executable name via: QueryFullProcessImageNameW
- Darwin (macOS): Available via
proc_name(macOS 10.4+).- BSD (FreeBSD): Available via
kinfo_getproc(theki_commfield in thekinfo_procstructure).gopsutil, the tool we use in hostmetricsreceiver scrapers, provides all of the above.Note
Initially, the idea was to make
process.executable.namerequired as this is available across all platforms. However, it was observed that calling execve() can replace the process at a certain PID, meaning the PID stays the same but other attributes such asprocess.executable.namecan change. For this reason, the descriptive attributes for the process have been changed tooptionaland the identity attributes remain required.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
[chore]