Move process executable to its own entity#3536
Move process executable to its own entity#3536jsuereth merged 12 commits intoopen-telemetry:mainfrom
Conversation
This is being done as per feedback from updating the process attributes requirement levels work.The advantage to moving process.executable to its own entity to to allow a relationship between process and process.executable, for example you could look at all processes beloning to a single executable.
Added build_id.go and build_id.gnu, build_id.htlhash
01a1e0e to
f17cec7
Compare
ChrsMark
left a comment
There was a problem hiding this comment.
LGTM
Let's file an issue for #3536 (comment) so we don't miss that.
New issue created #3563 |
braydonk
left a comment
There was a problem hiding this comment.
I usually don't press the "Request Changes" button cause it feels aggressive lol, just doing it here because my comment is intended to block merge.
|
@open-telemetry/specs-semconv-maintainers this is ready to be merged from the System SemConv SIG side :) |
it looks like there are still a couple of open conversations |
|
@braydonk could you review the conversations and close them if it makes sense? |
|
Looks like this needs |
This is done now, I merged with main and ran |
Fixes #3535
Changes
Move process.executable to its own entity
This is being done as per feedback from updating the process attributes
requirement levels work, see PR: #3461.
The advantage to moving process.executable to
its own entity to to allow a relationship between process and
process.executable, for example you could look at all processes belonging
to a single executable.
The new identifying attributes for the new entity
process.executableare:process.executable.nameprocess.executable.pathImportant
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]