DEVOPS-829 format Timer as summary/histogram type #893
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.
Description
Follow up PR to complete efforts from #881 as it did not produce the desired results. Digging in revealed that the metrics in question are registered as a Timer, not as Summary. Timer metrics are not part of the defined Prometheus metrics types.
This PR updates the Timer metric type to format and display as a Prometheus Summary metric (which I think was the intended behavior all along), consistent with the changes introduced in #881.
No breaking changes, all data previously presented by the metrics endpoint is still there. Formatting has been changed to follow Prometheus-type definitions, resulting in compatibility with the Open Telemetry Collector.
Changes
Checklist
Testing