[chore] manage jmx receiver lifecycle

[atoulme]

Handle the shutdown of the jmx receiver properly, providing a valid config so it can be created.

[runforesight]

Foresight Summary

    
Major Impacts

build-and-test-windows duration(6 seconds) has decreased 44 minutes 49 seconds compared to main branch avg(44 minutes 55 seconds).

View More Details

⭕  build-and-test-windows workflow has finished in 6 seconds (44 minutes 49 seconds less than main branch avg.) and finished at 13th Jan, 2023.

---

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

---

✅  check-links workflow has finished in 45 seconds (1 minute 14 seconds less than main branch avg.) and finished at 13th Jan, 2023.

---

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

---

✅  telemetrygen workflow has finished in 57 seconds (1 minute 34 seconds less than main branch avg.) and finished at 13th Jan, 2023.

---

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 5 seconds (1 minute 59 seconds less than main branch avg.) and finished at 13th Jan, 2023.

---

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

---

✅  tracegen workflow has finished in 1 minute 3 seconds (1 minute 29 seconds less than main branch avg.) and finished at 13th Jan, 2023.

---

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

---

✅  prometheus-compliance-tests workflow has finished in 3 minutes 17 seconds (4 minutes 42 seconds less than main branch avg.) and finished at 13th Jan, 2023.

---

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

---

 build-and-test workflow has finished in 16 minutes 9 seconds (32 minutes 51 seconds less than main branch avg.) and finished at 13th Jan, 2023.

---

Job	Failed Steps	Tests
unittest-matrix (1.19, internal)	N/A	✅ 640  ❌ 0  ⏭ 0    🔗	See Details
unittest-matrix (1.18, internal)	N/A	✅ 640  ❌ 0  ⏭ 0    🔗	See Details
correctness-metrics	N/A	✅ 2  ❌ 0  ⏭ 0    🔗	See Details
unittest-matrix (1.18, processor)	N/A	✅ 1481  ❌ 0  ⏭ 0    🔗	See Details
unittest-matrix (1.19, processor)	N/A	✅ 1481  ❌ 0  ⏭ 0    🔗	See Details
unittest-matrix (1.18, extension)	N/A	✅ 528  ❌ 0  ⏭ 0    🔗	See Details
unittest-matrix (1.19, extension)	N/A	✅ 528  ❌ 0  ⏭ 0    🔗	See Details
correctness-traces	N/A	✅ 17  ❌ 0  ⏭ 0    🔗	See Details
unittest-matrix (1.19, receiver-0)	N/A	✅ 2565  ❌ 0  ⏭ 0    🔗	See Details
unittest-matrix (1.18, receiver-0)	N/A	✅ 2565  ❌ 0  ⏭ 0    🔗	See Details
unittest-matrix (1.19, exporter)	N/A	✅ 2468  ❌ 0  ⏭ 0    🔗	See Details
unittest-matrix (1.18, exporter)	N/A	✅ 2468  ❌ 0  ⏭ 0    🔗	See Details
unittest-matrix (1.18, receiver-1)	N/A	✅ 1887  ❌ 0  ⏭ 0    🔗	See Details
unittest-matrix (1.19, receiver-1)	N/A	✅ 1887  ❌ 0  ⏭ 0    🔗	See Details
unittest-matrix (1.19, other)	N/A	✅ 4454  ❌ 0  ⏭ 0    🔗	See Details
unittest-matrix (1.18, other)	N/A	✅ 4454  ❌ 0  ⏭ 0    🔗	See Details
integration-tests	N/A	✅ 55  ❌ 0  ⏭ 0    🔗	See Details

---

✅  load-tests workflow has finished in 8 minutes 10 seconds (6 minutes 49 seconds less than main branch avg.) and finished at 13th Jan, 2023.

---

Job	Failed Steps	Tests
loadtest (TestTraceAttributesProcessor)	-     🔗	✅ 3  ❌ 0  ⏭ 0    🔗	See Details
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
setup-environment	-     🔗	N/A	See Details

---

🔎 See details on Foresight

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