[DRAFT] NOT MERGING POC: Send JVM runtime metrics via OTLP using OTel-native naming#10985

Draft

link04 wants to merge 12 commits intomasterfrom

maximo/otlp-runtime-metrics-poc

Commits on May 7, 2026

POC: Send JVM runtime metrics via OTLP using OTel-native naming

link04
and
claude
committed
Add missing JVM metrics: jvm.memory.init, jvm.buffer.*, jvm.system.cpu.utilization, jvm.class.count

link04
and
claude
committed
Wire JvmOtlpRuntimeMetrics into agent startup

link04
and
claude
committed
Rebase on master: fix imports for renamed OTLP classes

link04
and
claude
committed
Improve OTLP runtime metrics test: exact count, full list, no DD names

link04
and
claude
committed
Remove Opt-In JVM metrics from POC
link04
committed
Start OTLP runtime metrics from Agent boot, not OTel API advice
link04
committed
Drop Development-stability JVM metrics + migrate test to JUnit
link04
committed
Move OTLP runtime metrics start out of the JMX 15s delay
link04
committed
Remove redundant JvmOtlpRuntimeMetrics.start() from MeterProviderAdvice
link04
committed
Register JvmOtlpRuntimeMetrics for native-image reflection
link04
committed
Re-add Development-stability JVM metrics (non-opt-in)
link04
committed