Skip to content

Micrometer Prometheus client v1.x breaking changes #2340

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Micrometer Prometheus client v1.x breaking changes #2340

wants to merge 1 commit into from
+98 −0

Conversation

@brunobat
Copy link
Contributor

@brunobat brunobat commented Jun 18, 2025 •
edited
Loading

This is a blog post to communicate the Micromenter Prometheus client v1.x changes.

@github-actions
Copy link

github-actions bot commented Jun 18, 2025 •
edited
Loading

🎊 PR Preview 5bb6532 has been successfully built and deployed to https://quarkus-site-pr-2340-preview.surge.sh

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

nderwin
nderwin reviewed Jun 18, 2025
View reviewed changes
nderwin
nderwin reviewed Jun 18, 2025
View reviewed changes
@gastaldi gastaldi requested a review from Copilot June 18, 2025 17:26
Copilot AI reviewed Jun 18, 2025
View reviewed changes
Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull Request Overview

This PR introduces a new documentation post detailing the migration paths and breaking changes resulting from the switch to Prometheus client v1 in the Micrometer registry.

  • Introduces a new post explaining upgrade options and dependency changes
  • Details specific changes to metrics naming and API usage

@brunobat brunobat marked this pull request as draft June 20, 2025 07:43
@brunobat
Copy link
Contributor Author

brunobat commented Jun 20, 2025 •
edited
Loading

There is a plan change:

  1. Keep current extension as is until Quarkus 4.0 (whenever that happens)
  2. Create a new extension called quarkus-micrometer-registry-prometheus-v1 now
  3. Delete current quarkus-micrometer-registry-prometheus on Quarkus 4.0. Provide alternative on Quarkiverse.
  4. Refactor: Stramline the main extension (quarkus-micrometer) and quarkus-micrometer-registry-prometheus-v1 to remove outdated code on Quarkus 4.0.
  5. On the next LTS it would be good to mark for deprecation the old registry and support the new one.

Will re-write the blog to reflect that.

@brunobat
Copy link
Contributor Author

brunobat commented Jun 20, 2025 •
edited
Loading

Re-wrote the post according to the new plan and zulip coments.
I still need to come up with better examples for the changes.
Will finish when I know when we will release the new extension.

@brunobat
Copy link
Contributor Author

brunobat commented Jul 2, 2025

This is on hold due to other ongoing work.

@brunobat
Copy link
Contributor Author

brunobat commented Oct 20, 2025

Updated the post. It's now ready to review.

@brunobat brunobat marked this pull request as ready for review October 20, 2025 16:22
@brunobat brunobat changed the title Micrometer Prometheus client v1.0 breaking changes Micrometer Prometheus client v1.x breaking changes Oct 20, 2025
cescoffier
cescoffier requested changes Oct 20, 2025
View reviewed changes
Copy link
Member

@cescoffier cescoffier left a comment

Choose a reason for hiding this comment

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

I need to read it again on my machine (on my phone now).

We should also advertise the working group

_posts/2025-11-07-micrometer-prometheus-v1.adoc

Micrometer has become the default metrics framework in Quarkus due to its stability, maturity, and widespread adoption on the Java ecosystem — not https://quarkus.io/guides/opentelemetry-metrics[OpenTelemetry Metrics].

Micrometer support in Quarkus is built on top af a main extension `quarkus-micrometer`, then specific registries extensions include it as a dependency and implement a registry sending out the telemetry. The Prometheus registry (`quarkus-micrometer-registry-prometheus`) is the default and most commonly used, and it is the focus of this announcement.
Copy link
Member

@cescoffier cescoffier Oct 20, 2025

Choose a reason for hiding this comment

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

Of not af :-)

@brunobat
Copy link
Contributor Author

brunobat commented Oct 21, 2025

I need to read it again on my machine (on my phone now).

We should also advertise the working group

I can publicize this in that discussion but this is not part of the scope of that group.

cescoffier
cescoffier requested changes Oct 21, 2025
View reviewed changes
@brunobat brunobat requested a review from cescoffier October 31, 2025 15:20
@brunobat
Copy link
Contributor Author

brunobat commented Oct 31, 2025

@cescoffier can you please re-review.

cescoffier
cescoffier requested changes Nov 3, 2025
View reviewed changes
_posts/2025-11-07-micrometer-prometheus-v1.adoc
====

=== Quarkus migration plan

Copy link
Member

@cescoffier cescoffier Nov 3, 2025

Choose a reason for hiding this comment

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

To migrate to the new extension, follow these steps:

_posts/2025-10-31-micrometer-prometheus-v1.adoc Outdated

=== Quarkus migration plan

1. Keep current extension as is until Quarkus 4.0 (whenever that happens) so users can migrate at a time of their choice.
Copy link
Member

@cescoffier cescoffier Nov 3, 2025

Choose a reason for hiding this comment

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

  1. You can keep using the deprecated extension until Quarkus 4.0, so you can do it at your own time.

brunobat
brunobat commented Nov 7, 2025
View reviewed changes
Copy link
Contributor Author

@brunobat brunobat left a comment

Choose a reason for hiding this comment

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

About the migration plan, I've re-wrote it to match the user's point of view.

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

Reviewers

Copilot code review Copilot Copilot left review comments

@cescoffier cescoffier cescoffier requested changes

@insectengine insectengine Awaiting requested review from insectengine

+1 more reviewer

@nderwin nderwin nderwin left review comments

Reviewers whose approvals may not affect merge requirements

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

3 participants

@brunobat @cescoffier @nderwin