You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Process semconv: define common attributes and revisit requirement levelsΒ #864
As a result, users would get inconsistent data from different systems and instrumentations.
Vendors will need to know how to parse and extract specific details (such as process name).
Describe the solution you'd like
The approach we follow in HTTP and other semconv:
Find 1-2 required attributes (e.g. process.executable.name) which are available everywhere
Require instrumentations to do the parsing/extraction of this common information so that users and consumers would get consistent data
Set appropriate requirement levels on other attributes
Discussed on 2024-12-12 System SemConv WG meeting. We can take care of this as part of defining processes as Entities. The place to put this information down as YAML is not ready yet but we can work on this in parallel.
@dmitryax has a doc where we are working on this. He will create an issue for defining processes as an entitity and mark this as blocked on that issue.
@/dmitryax has a doc where we are working on this. He will create an issue for defining processes as an entitity and mark this as blocked on that issue.
Just looking at this, correct me if I am wrong, we need to update our process common attributes and make some required. For example, this would mean making process.executable.name required instead of conditionally_required. The idea is we want to make a few attributes required that are consistently available across all platforms, for example, process.executable.name should be available across, Linux, Windows, and Darwin.
The collector-contrib hostmetrics receiver already provides this attribute by default, but the question is: how would other instrumentations in language SDKs need to change with this update? Looking at the opentelemtry-go sdk, this is not enabled by default, see here.
Happy to help here and open a draft PR if that works? cc. @braydonk
However the mentioned PR doesn't seem to change any of those but rather set the requirement level for a few others.
Can we clarify if #3107 is the only thing missing and update this issue accordingly?
It seems that the current issue is the only blocker for promoting process.* to release_candidate based on #3041, which is something we can target soon hopefully before KubeConEU (26') :) .
It turns out we have 2 different issues to cover. One is to revisit Process Entity and its attributes and the second is to cover metrics' attributes and their requirement levels. See #3041 (comment).
Activity
ChrsMark commentedon Apr 8, 2024
cc: @open-telemetry/semconv-system-approvers
mx-psi commentedon Dec 12, 2024
Discussed on 2024-12-12 System SemConv WG meeting. We can take care of this as part of defining processes as Entities. The place to put this information down as YAML is not ready yet but we can work on this in parallel.
@dmitryax has a doc where we are working on this. He will create an issue for defining processes as an entitity and mark this as blocked on that issue.
mx-psi commentedon Jan 16, 2025
See #1751, marking this as blocked
ChrsMark commentedon Oct 2, 2025
I think that's also related to #626 which was discussed in the past.
osullivandonal commentedon Feb 6, 2026
Just looking at this, correct me if I am wrong, we need to update our process common attributes and make some required. For example, this would mean making
process.executable.namerequired instead of conditionally_required. The idea is we want to make a few attributes required that are consistently available across all platforms, for example,process.executable.nameshould be available across, Linux, Windows, and Darwin.The collector-contrib hostmetrics receiver already provides this attribute by default, but the question is: how would other instrumentations in language SDKs need to change with this update? Looking at the opentelemtry-go sdk, this is not enabled by default, see here.
Happy to help here and open a draft PR if that works? cc. @braydonk
braydonk commentedon Feb 6, 2026
Thanks @osullivandonal, my PR #3107 should pretty much cover this issue but I need to go back and reopen it addressing the comments.
ChrsMark commentedon Feb 10, 2026
@braydonk @osullivandonal just double checking on this since I'm a bit confused about the current state π .
The original description of this issue is about revisiting the requirement levels of the following:
semantic-conventions/docs/resource/process.md
Lines 39 to 45 in a04a1f4
However the mentioned PR doesn't seem to change any of those but rather set the requirement level for a few others.
Can we clarify if #3107 is the only thing missing and update this issue accordingly?
It seems that the current issue is the only blocker for promoting
process.*torelease_candidatebased on #3041, which is something we can target soon hopefully before KubeConEU (26') :) .ChrsMark commentedon Feb 12, 2026
It turns out we have 2 different issues to cover. One is to revisit Process Entity and its attributes and the second is to cover metrics' attributes and their requirement levels. See #3041 (comment).
mx-psi commentedon Mar 25, 2026
This was fixed by #3461 and #3548
Generate and upgrade to `semconv/v1.41.0` (#8324)