Skip to content

Conversation

@gsmet
Copy link
Member

@gsmet gsmet commented Oct 21, 2025

No description provided.

@quarkus-bot
Copy link

quarkus-bot bot commented Oct 21, 2025

Thanks for your pull request!

Your pull request does not follow our editorial rules. Could you have a look?

  • description should not be empty, describe your intent or provide links to the issues this PR is fixing (using Fixes #NNNNN) or changelogs

This message is automatically generated by a bot.

@quarkus-bot quarkus-bot bot added the area/infra-automation anything related to CI, bots, etc. that are used to automated our infrastructure label Oct 21, 2025
@rsvoboda
Copy link
Member

@gsmet could you trigger full run? e.g. some minor change in root or bom pom.xml ...

@github-actions
Copy link

github-actions bot commented Oct 30, 2025

🎊 PR Preview 5847d4c has been successfully built and deployed to https://quarkus-pr-main-50651-preview.surge.sh/version/main/guides/

  • Images of blog posts older than 3 months are not available.
  • Newsletters older than 3 months are not available.

"Recent CPU utilization for the process as reported by the JVM.", "1", DOUBLE_GAUGE));
jvmMetrics.add(new MetricToAssert("jvm.thread.count", "Number of executing platform threads.", "{thread}", LONG_SUM));

// not supported on Semeru
Copy link
Member

@rsvoboda rsvoboda Nov 5, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@brunobat shouldn't otel docs mention these limitations (once we have semeru testing/support in) ?

Edit: I checked https://github.com/microprofile/microprofile-telemetry/blob/2.0/spec/src/main/asciidoc/metrics.adoc#required-metrics to be sure we don't have trouble on MicroProfile Telemetry front with Semeru. These metrics are not mandatory.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@rsvoboda we already report that we don't support those OTel Metrics on native. Please check the list in here: https://quarkus.io/guides/opentelemetry-metrics#microprofile-2-0

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Native comment is not on these ...

        if (!JdkUtil.isSemeru()) {
            jvmMetrics.add(new MetricToAssert("jvm.cpu.limit", "", "1", LONG_SUM));
            jvmMetrics.add(new MetricToAssert("jvm.cpu.longlock", "Long lock times", "s", HISTOGRAM));
            jvmMetrics.add(new MetricToAssert("jvm.cpu.context_switch", "", "Hz", DOUBLE_SUM));


if (!collector.isRecording()) {
LOGGER.warning(
"Recording JFR events is not supported by this VM, @ShouldPin and @ShouldNotPin annotations are not enforced.");
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Something we should have in Quarkus docs too.

Probably in src/main/asciidoc/jfr.adoc and src/main/asciidoc/observability.adoc

Maybe a general guide with JDKs details / limits ?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah maybe but then I'm not really a fan of documenting the limitations of various JDKs, and updating them when new versions pop up.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area/infra-automation anything related to CI, bots, etc. that are used to automated our infrastructure area/testing

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants