Uh oh!
There was an error while loading. Please reload this page.
Allow duplicate metric names - #1728
Conversation
b9e17cf to
97348f6CompareUh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
509709c to
f56241eCompareSigned-off-by: Jay DeLuca <jaydeluca4@gmail.com>
Signed-off-by: Jay DeLuca <jaydeluca4@gmail.com>
Signed-off-by: Jay DeLuca <jaydeluca4@gmail.com>
Signed-off-by: Jay DeLuca <jaydeluca4@gmail.com>
Signed-off-by: Jay DeLuca <jaydeluca4@gmail.com>
Signed-off-by: Jay DeLuca <jaydeluca4@gmail.com>
Signed-off-by: Jay DeLuca <jaydeluca4@gmail.com>
Signed-off-by: Jay DeLuca <jaydeluca4@gmail.com>
f56241e to
a900419CompareUh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Pull request overview
This PR enables multiple metrics with the same Prometheus name but different label sets to coexist, addressing a limitation where duplicate metric names were previously rejected at registration time. The validation has been moved from registration to scrape time, where it now checks for type consistency and unique label combinations. During exposition, metrics with the same name are merged under a single HELP/TYPE declaration.
Key changes:
- Registration no longer rejects duplicate metric names; validation occurs at scrape time
- Metrics with the same name but different types or duplicate label sets throw exceptions at scrape time
- Exposition formats merge duplicate metric names into single metric families with combined data points
Reviewed changes
Copilot reviewed 16 out of 16 changed files in this pull request and generated 6 comments.
Show a summary per file
| File | Description |
|---|---|
| PrometheusRegistry.java | Removed duplicate name checking at registration time and during scrape |
| Collector.java | Updated documentation to remove reference to registration-time name checking |
| MultiCollector.java | Updated documentation to remove reference to registration-time name checking |
| MetricSnapshots.java | Added validation logic for type consistency and duplicate label detection at construction time |
| TextFormatUtil.java | Added mergeDuplicates() method to combine snapshots with the same Prometheus name |
| PrometheusTextFormatWriter.java | Integrated mergeDuplicates() to ensure single HELP/TYPE per metric family |
| OpenMetricsTextFormatWriter.java | Integrated mergeDuplicates() for OpenMetrics format |
| PrometheusProtobufWriterImpl.java | Integrated mergeDuplicates() for protobuf format |
| PrometheusRegistryTest.java | Added comprehensive tests for duplicate name scenarios |
| TextFormatUtilTest.java | Added tests for the mergeDuplicates functionality |
| DuplicateNamesExpositionTest.java | New test file validating duplicate names in text formats |
| DuplicateNamesProtobufTest.java | New test file validating duplicate names in protobuf format |
| DuplicateMetricsIT.java | New integration test for end-to-end duplicate metrics validation |
| DuplicateMetricsSample.java | New sample application demonstrating duplicate metrics usage |
| pom.xml files | Added new test module to build configuration |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
jaydeluca
commented
Jan 26, 2026
closing in favor of #1800 |
Closes#696 Alternate approach to #1728 Validation occurs at registration time: - Metrics with the same name, type, unit, and help - but different labels, are allowed to be registered - Custom Collectors that do not implement the required fields (prometheus name, metric type) will skip validation and could risk creating duplicate series that will cause issues at scrape time. - I looked into adding a fallback, but it requires calling `collect()` at registration in order to introspect existing metadata and that seemed not great due to potential side effects --------- Signed-off-by: Jay DeLuca <jaydeluca4@gmail.com>
Resolves#696
The goal of this change is to be able to have multiple metrics with the same name but different labels, which had previously been prevented by a check during registration.
While implementing this, I operated under a few assumptions:
I originally attempted to implement the validation during metric registration, but that required doing some things that felt wrong, so I moved the validation to scrape time. This does result in a bit of a performance hit (~10% reduction in op/s in the benchmarks I ran) on the scrape operation.
The benchmarks I ran were on an apple M4. I did 4 runs total - 2 of the main branch for a baseline and 2 for this feature branch and then averaged them.
Benchmark results
TextFormatUtilBenchmark
CounterBenchmark
HistogramBenchmark