Area(s)
area:process
What's missing?
When updating the process attribute requirement levels in #3461 it was discussed moving process.executable to its own entity. Currently process.executable.name and process.executable.path are descriptive attributes for the process entity. See conversation here.
The advantage to this is that it would allow us to have a relationship between process and process.executable. This would allow us to see all processes using a single executable. Allowing easier filtering etc.
cc. @thompson-tomo
Describe the solution you'd like
The solution would be to move process.executable to its own entity and use:
process.executable.path
process.executable.name
as identifying attributes.
Tip
React with 👍 to help prioritize this issue. Please use comments to provide useful context, avoiding +1 or me too, to help us triage it. Learn more here.
Area(s)
area:process
What's missing?
When updating the process attribute requirement levels in #3461 it was discussed moving
process.executableto its own entity. Currentlyprocess.executable.nameandprocess.executable.pathare descriptive attributes for theprocessentity. See conversation here.The advantage to this is that it would allow us to have a relationship between
processandprocess.executable. This would allow us to see all processes using a single executable. Allowing easier filtering etc.cc. @thompson-tomo
Describe the solution you'd like
The solution would be to move
process.executableto its own entity and use:process.executable.pathprocess.executable.nameas identifying attributes.
Tip
React with 👍 to help prioritize this issue. Please use comments to provide useful context, avoiding
+1orme too, to help us triage it. Learn more here.