[receiver/hostmetrics] Remove shared from system.memory.state values

[ChrsMark]

Component(s)

receiver/hostmetrics

Describe the issue you're reporting

If open-telemetry/semantic-conventions#933 is merged we will need to change the receiver implementation accordingly.

ref: open-telemetry/semantic-conventions#522

[github-actions]

Pinging code owners:

• receiver/hostmetrics: @dmitryax @braydonk

%s See Adding Labels via Comments if you do not have permissions to add labels yourself.

[crobert-1]

Hopefully not taking this out of context, but a code owner's response on another issue seems to agree with this decision as well.

Removing needs triage.

[github-actions]

This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping @open-telemetry/collector-contrib-triagers. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.

Pinging code owners:

• receiver/hostmetrics: @dmitryax @braydonk

See Adding Labels via Comments if you do not have permissions to add labels yourself.

[rogercoll]

Still important for v1. Once slab memory is available in the semantic conventions, we could implement the shared + slab removal under the same feature gate.

[github-actions]

This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping @open-telemetry/collector-contrib-triagers. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.

Pinging code owners:

• receiver/hostmetrics: @dmitryax @braydonk

See Adding Labels via Comments if you do not have permissions to add labels yourself.

[github-actions]

This issue has been closed as inactive because it has been stale for 120 days with no activity.