Otel Java agent 1.13.0 renamed JVM GC metrics to follow Otel Semantic Conventions

[cyrille-leclerc]

The Otel Java agent 1.13.0 renamed JVM GC metrics to follow the OpenTelemetry Semantic Conventions for JVM metrics

Old metrics:

runtime.jvm.memory.area{type="used",area="heap"} 2000000
runtime.jvm.memory.area{type="committed",area="non_heap"} 200000
runtime.jvm.memory.area{type="used",pool="PS Eden Space"} 2000

New metrics:

 process.runtime.jvm.memory.init{type="heap",pool="G1 Eden Space"} 1000000
 process.runtime.jvm.memory.usage{type="heap",pool="G1 Eden Space"} 2500000
 process.runtime.jvm.memory.committed{type="heap",pool="G1 Eden Space"} 3000000
 process.runtime.jvm.memory.max{type="heap",pool="G1 Eden Space"} 4000000
 process.runtime.jvm.memory.init{type="non_heap",pool="Metaspace"} 200
 process.runtime.jvm.memory.usage{type="non_heap",pool="Metaspace"} 400
 process.runtime.jvm.memory.committed{type="non_heap",pool="Metaspace"} 500

See new code https://raw.githubusercontent.com/open-telemetry/opentelemetry-java-instrumentation/v1.13.1/instrumentation/runtime-metrics/library/src/main/java/io/opentelemetry/instrumentation/runtimemetrics/MemoryPools.java

[cyrille-leclerc]

@AlexanderWert could you please help us map the new Otel metrics to the Elastic APM GUI metrics?

@AlexanderWert @axw I'm wondering if we could just break compatibility and only support the new metric names, dropping the support for the metrics emitted by Otel Java agents 1.12-. What do you think?