MicroProfile Telemetry 2.0

[radcortez]

No description provided.

[brunobat]

@radcortez Seems that we need to set otel.metric.export.interval=3000 to make the runs reproducible.
Does this fix the flaky tests?
(EDIT)
I see that <otel.metric.export.interval>3000</otel.metric.export.interval> is already set...
Do you have have a list of the flaky tests?

[radcortez]

The Flaky tests are all in the JVM package: https://github.com/eclipse/microprofile-telemetry/tree/877f460eb1c3675102b2b5038cb48dec6d99bf92/tck/metrics/src/main/java/org/eclipse/microprofile/telemetry/metrics/tck/jvm

I haven't looked into the details yet. I suspect that the metrics collection for JVM attributes just takes longer than the configured export interval.

[brunobat]

The Flaky tests are all in the JVM package: https://github.com/eclipse/microprofile-telemetry/tree/877f460eb1c3675102b2b5038cb48dec6d99bf92/tck/metrics/src/main/java/org/eclipse/microprofile/telemetry/metrics/tck/jvm

I haven't looked into the details yet. I suspect that the metrics collection for JVM attributes just takes longer than the configured export interval.

CC @Emily-Jiang

[radcortez]

The problem is that the number of metrics generated cycles the log file, so there may be occasions where the metrics collected are not in the file anymore. The log file cannot be cycled.

[Emily-Jiang]

@radcortez @brunobat can you try out this PR to see whether it fixes your issue?

[Emily-Jiang]

I have restaged the Telemetry 2.0 release here with the above fix. Please try it out @brunobat @radcortez

[radcortez]

It consistently fails in JvmGarbageCollectionTest with JDK 11 (confirmed locally). However, it does work fine with JDK 17 and 21. We use the implementation provided by OpenTelemetry.

It seems that with JDK 11, there is not a single GC during the test execution, so the metric is not generated. Apparently it does work by hinting a System.gc() in the test method.