You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There were several related but different problems involving multiple metrics having the same name (which is permitted if they have different tags).
The Prometheus/OpenMetrics output mandates that the TYPE for a given metric must appear only once in the output. The ConcurrentGauge and Meter implementations did not honor this requirement.
The /metrics/{registry}/{metricName} endpoint returns only a single metric but should return all metrics matching the name, regardless of tags.
Steps to reproduce
Create multiple metrics of the same metric type sharing the same name bug different tags, then access the application's /metrics/{registry}/{metricName} endpoint. The output reports only one metric instance, not all of them. The problems with ConcurrentGauge and Meter appeared when that first issue was corrected.
The text was updated successfully, but these errors were encountered:
Environment Details
Problem Description
There were several related but different problems involving multiple metrics having the same name (which is permitted if they have different tags).
The Prometheus/OpenMetrics output mandates that the
TYPE
for a given metric must appear only once in the output. TheConcurrentGauge
andMeter
implementations did not honor this requirement.The
/metrics/{registry}/{metricName}
endpoint returns only a single metric but should return all metrics matching the name, regardless of tags.Steps to reproduce
Create multiple metrics of the same metric type sharing the same name bug different tags, then access the application's
/metrics/{registry}/{metricName}
endpoint. The output reports only one metric instance, not all of them. The problems withConcurrentGauge
andMeter
appeared when that first issue was corrected.The text was updated successfully, but these errors were encountered: