[receiver/hostmetrics] Add optional metric process.memory.utilization

[andrzej-stencel]

Description:

This pull request adds a new optional metric named process.memory.utilization to the metrics scraped by the process scraper of the hostmetrics receiver.

Adding this metric to the semantic conventions has been proposed here:

• Add process.memory.utilization metric opentelemetry-specification#2811.

There's a related system metric system.memory.utilization available in the memory scraper.

Link to tracking Issue:

• Enhance hostmetrics receiver process scraper to bring it closer to parity with telegraf procstat provided metrics #14084

[github-actions]

This PR was marked stale due to lack of activity. It will be closed in 14 days.

[dmitryax]

please rebase

[andrzej-stencel]

@dmitryax please take a look at this freshly rebased change

[github-actions]

This PR was marked stale due to lack of activity. It will be closed in 14 days.

[runforesight]

Foresight Summary

    
Major Impacts

TestConsumeLogsUnexpectedExporterType ❌ failed 2 times in 4 runs (50% fail rate).

TestConsumeTracesUnexpectedExporterType ❌ failed 2 times in 4 runs (50% fail rate).

TestLoadInvalidConfig_NoScrapers ❌ failed 2 times in 3 runs (66% fail rate).

build-and-test-windows duration(4 seconds) has decreased 39 minutes 47 seconds compared to main branch avg(39 minutes 51 seconds).

View More Details

⭕  build-and-test-windows workflow has finished in 4 seconds (39 minutes 56 seconds less than main branch avg.) and finished at 13th Dec, 2022.

---

Job	Failed Steps	Tests
windows-unittest-matrix	-     🔗	N/A	See Details
windows-unittest	-     🔗	N/A	See Details

---

✅  tracegen workflow has finished in 1 minute 31 seconds (2 minutes 10 seconds less than main branch avg.) and finished at 13th Dec, 2022.

---

Job	Failed Steps	Tests
build-dev	-     🔗	N/A	See Details
publish-latest	-     🔗	N/A	See Details
publish-stable	-     🔗	N/A	See Details

---

✅  changelog workflow has finished in 2 minutes 32 seconds (4 minutes 54 seconds less than main branch avg.) and finished at 13th Dec, 2022.

---

Job	Failed Steps	Tests
changelog	-     🔗	N/A	See Details

---

✅  check-links workflow has finished in 2 minutes 39 seconds (42 seconds less than main branch avg.) and finished at 13th Dec, 2022.

---

Job	Failed Steps	Tests
changed files	-     🔗	N/A	See Details
check-links	-     🔗	N/A	See Details

---

✅  prometheus-compliance-tests workflow has finished in 3 minutes 30 seconds (5 minutes 58 seconds less than main branch avg.) and finished at 13th Dec, 2022.

---

Job	Failed Steps	Tests
prometheus-compliance-tests	-     🔗	✅ 21  ❌ 0  ⏭ 0    🔗	See Details

---

✅  load-tests workflow has finished in 12 minutes 24 seconds (4 minutes 3 seconds less than main branch avg.) and finished at 13th Dec, 2022.

---

Job	Failed Steps	Tests
loadtest (TestIdleMode)	-     🔗	✅ 1  ❌ 0  ⏭ 0    🔗	See Details
loadtest (TestMetric10kDPS|TestMetricsFromFile)	-     🔗	✅ 6  ❌ 0  ⏭ 0    🔗	See Details
loadtest (TestTraceNoBackend10kSPS|TestTrace1kSPSWithAttrs)	-     🔗	✅ 8  ❌ 0  ⏭ 0    🔗	See Details
loadtest (TestMetricResourceProcessor|TestTrace10kSPS)	-     🔗	✅ 12  ❌ 0  ⏭ 0    🔗	See Details
loadtest (TestTraceBallast1kSPSWithAttrs|TestTraceBallast1kSPSAddAttrs)	-     🔗	✅ 10  ❌ 0  ⏭ 0    🔗	See Details
loadtest (TestBallastMemory|TestLog10kDPS)	-     🔗	✅ 19  ❌ 0  ⏭ 0    🔗	See Details
loadtest (TestTraceAttributesProcessor)	-     🔗	✅ 3  ❌ 0  ⏭ 0    🔗	See Details
setup-environment	-     🔗	N/A	See Details

---

❌  build-and-test workflow has finished in 41 minutes 57 seconds (19 minutes 11 seconds less than main branch avg.) and finished at 13th Dec, 2022. 1 job failed. There are 6 test failures.

---

Job	Failed Steps	Tests
unittest-matrix (1.18, internal)	-     🔗	✅ 592  ❌ 0  ⏭ 0    🔗	See Details
unittest-matrix (1.19, processor)	-     🔗	✅ 1465  ❌ 0  ⏭ 0    🔗	See Details
unittest-matrix (1.18, extension)	-     🔗	✅ 528  ❌ 0  ⏭ 0    🔗	See Details
unittest-matrix (1.19, internal)	-     🔗	✅ 592  ❌ 0  ⏭ 0    🔗	See Details
correctness-metrics	-     🔗	✅ 2  ❌ 0  ⏭ 0    🔗	See Details
unittest-matrix (1.19, extension)	-     🔗	✅ 528  ❌ 0  ⏭ 0    🔗	See Details
unittest-matrix (1.18, processor)	-     🔗	✅ 1465  ❌ 0  ⏭ 0    🔗	See Details
correctness-traces	-     🔗	✅ 17  ❌ 0  ⏭ 0    🔗	See Details
unittest-matrix (1.18, receiver-0)	-     🔗	✅ 2534  ❌ 1  ⏭ 0    🔗	See Details
unittest-matrix (1.19, receiver-0)	-     🔗	✅ 2534  ❌ 1  ⏭ 0    🔗	See Details
unittest-matrix (1.19, exporter)	-     🔗	✅ 2237  ❌ 2  ⏭ 0    🔗	See Details
unittest-matrix (1.18, other)	-     🔗	✅ 4363  ❌ 0  ⏭ 0    🔗	See Details
unittest-matrix (1.18, exporter)	-     🔗	✅ 2237  ❌ 2  ⏭ 0    🔗	See Details
unittest-matrix (1.18, receiver-1)	-     🔗	✅ 1854  ❌ 0  ⏭ 0    🔗	See Details
unittest-matrix (1.19, other)	-     🔗	✅ 4363  ❌ 0  ⏭ 0    🔗	See Details
unittest-matrix (1.19, receiver-1)	-     🔗	✅ 1854  ❌ 0  ⏭ 0    🔗	See Details
integration-tests	-     🔗	✅ 53  ❌ 0  ⏭ 0    🔗	See Details
setup-environment	-     🔗	N/A	See Details
check-collector-module-version	-     🔗	N/A	See Details
checks	-     🔗	N/A	See Details
check-codeowners	-     🔗	N/A	See Details
lint-matrix (receiver-0)	-     🔗	N/A	See Details
lint-matrix (receiver-1)	-     🔗	N/A	See Details
lint-matrix (processor)	-     🔗	N/A	See Details
lint-matrix (exporter)	-     🔗	N/A	See Details
lint-matrix (extension)	-     🔗	N/A	See Details
lint-matrix (internal)	-     🔗	N/A	See Details
lint-matrix (other)	-     🔗	N/A	See Details
build-examples	-     🔗	N/A	See Details
lint	-     🔗	N/A	See Details
unittest (1.19)	-     🔗	N/A	See Details
unittest (1.18)	-     🔗	N/A	See Details
cross-compile (darwin, amd64)	-     🔗	N/A	See Details
cross-compile (darwin, arm64)	-     🔗	N/A	See Details
cross-compile (linux, 386)	-     🔗	N/A	See Details
cross-compile (linux, amd64)	-     🔗	N/A	See Details
cross-compile (linux, arm)	-     🔗	N/A	See Details
cross-compile (linux, arm64)	-     🔗	N/A	See Details
cross-compile (linux, ppc64le)	-     🔗	N/A	See Details
cross-compile (windows, 386)	-     🔗	N/A	See Details
cross-compile (windows, amd64)	-     🔗	N/A	See Details
build-package (deb)	Test deb package     🔗	N/A	See Details
build-package (rpm)	-     🔗	N/A	See Details
windows-msi	-     🔗	N/A	See Details
publish-check	-     🔗	N/A	See Details
publish-dev	-     🔗	N/A	See Details
publish-stable	-     🔗	N/A	See Details

---

🔎 See details on Foresight

^{*You can configure Foresight comments in your organization settings page.}

[andrzej-stencel]

@dmitryax any chance this optional metric can be added? (the build package (deb) job failure doesn't seem related to my changes).

[dmitryax]

@astencel-sumo it's unclear from the docs and unit if the metric is emitted in a fraction of 1 of percentage. I believe it's the same issue for other "utilization" metrics in hostreceiver. Maybe even not well defined in the spec. Can you please help with making it consistent and clear?