feat: use typed Prometheus family descriptors#7487
Open
zeitlinger wants to merge 11 commits into
Open
Conversation
Signed-off-by: Gregor Zeitlinger <gregor.zeitlinger@grafana.com>
Signed-off-by: Gregor Zeitlinger <gregor.zeitlinger@grafana.com>
Signed-off-by: Gregor Zeitlinger <gregor.zeitlinger@grafana.com>
Signed-off-by: Gregor Zeitlinger <gregor.zeitlinger@grafana.com>
Signed-off-by: Gregor Zeitlinger <gregor.zeitlinger@grafana.com>
Signed-off-by: Gregor Zeitlinger <gregor.zeitlinger@grafana.com>
Signed-off-by: Gregor Zeitlinger <gregor.zeitlinger@grafana.com>
Signed-off-by: Gregor Zeitlinger <gregor.zeitlinger@grafana.com>
Signed-off-by: Gregor Zeitlinger <gregor.zeitlinger@grafana.com>
Signed-off-by: Gregor Zeitlinger <gregor.zeitlinger@grafana.com>
1 task
Signed-off-by: Gregor Zeitlinger <gregor.zeitlinger@grafana.com>
zeitlinger
added a commit
to prometheus/client_java
that referenced
this pull request
Jun 5, 2026
## Summary - Points the `typed-descriptor` compat matrix leg at the latest head of [micrometer-metrics/micrometer#7487](micrometer-metrics/micrometer#7487) (`84092837e`), which now builds against client_java 1.7.0 and uses the typed `MetricFamilyDescriptor` API. - Updates renovate `currentValue` to match the actual PR branch (`feat/prom-client-java-typed-family-descriptor`). ## Test plan - [ ] Micrometer Compatibility workflow `typed-descriptor` leg passes --------- Signed-off-by: Gregor Zeitlinger <gregor.zeitlinger@grafana.com>
Member
|
@zeitlinger thank you for the PR. We'll look to review and merge this for the Micrometer 1.18.0 release. In the meantime, dependabot sent a PR to upgrade the Prometheus Java client version to 1.7.0, which was merged automatically since the build passed: #7572. That would be included in the upcoming Micrometer 1.17.0 GA release. Is there any concern about making that upgrade on its own without this PR? |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
This is a cleaner follow-up to the Prometheus metadata compatibility work for Micrometer.
Instead of reconstructing
MetricMetadatafrom Micrometer-side suffix logic, this change switches the Prometheus registry integration to use the new typed registration descriptor API fromclient_java.Depends on:
Related context:
What changed
MetricFamilyDescriptorMetricMetadatareconstruction for registration metadataWhy
Micrometer needs registration-time family metadata for collision validation, but the old shape forced Micrometer to duplicate Prometheus naming derivation details.
With
client_javaexposing typed family descriptors, Micrometer can now treat Prometheus metadata as an upstream concern instead of rebuilding it locally.Validation
Tested locally against a locally installed
prometheus/client_java1.6.2-SNAPSHOTcontaining the descriptor API from prometheus/client_java#2114:Notes
prometheus/client_java#2114first.